[cfe-commits] bitfield.c fails
daniel at zuster.org
Mon Dec 1 17:28:57 PST 2008
This sounds like the kind of test case I would write. :)
At the time this was my attempt to get a test case which had some
stronger connection to correctness than just "IRgen didn't crash/give
an error", but perhaps the right thing to do is just make an
executable test case out of it and move it into llvm-test? OTOH, it is
also nice to know that the optimizer does end up cleaning up these
things for the kind of code we generate.
Chris, do you have an opinion on whether using the optimizer to
canonicalize test cases is good or bad?
On Mon, Dec 1, 2008 at 4:57 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
> It appears to be my fault... AFAIK, the generated code isn't actually
> broken, it's just that it depends on the LLVM optimizers to fold
> accurately for the test to work. And in this case, the LLVM
> optimizers are being stupid; see PR3152.
> On Mon, Dec 1, 2008 at 3:58 PM, Fariborz Jahanian <fjahanian at apple.com> wrote:
>> Hi All,
>> CodeGen/bitfield.c has been failing since the break. Any one knows why?
>> - Fariborz
>> cfe-commits mailing list
>> cfe-commits at cs.uiuc.edu
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
More information about the cfe-commits