{"push_id":609992168,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e86dbbf0583dd256ee469160a598f848cadd03e5","before":"858c62e51ee983e22915f748447ecef52b432851","commits":[{"sha":"e86dbbf0583dd256ee469160a598f848cadd03e5","author":{"email":"76a8e82c3bdc78a1f9490a34857cdee8b1b06a45@anl.gov","name":"Hal Finkel"},"message":"[SDAG] Don't widen VSETCC during type legalization for split operands\n\nBecause the operands of a vector SETCC node can be of a different type from the\nresult (and often are), it can happen that even if we'd prefer to widen the\nresult type of the SETCC, the operands have been split instead. In this case,\nthe SETCC result also must be split. This mirrors what is done in\nWidenVecRes_SELECT, and should be NFC elsewhere because if the operands are not\nwidened the following calls to GetWidenedVector will assert (which is what was\nhappening in the test case).\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@232935 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-mirror/llvm/commits/e86dbbf0583dd256ee469160a598f848cadd03e5"}]}