This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/16437] New c-torture failures after bitfield patch
- From: "dnovillo at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jul 2004 16:27:59 -0000
- Subject: [Bug tree-optimization/16437] New c-torture failures after bitfield patch
- References: <20040708153002.16437.dnovillo@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From dnovillo at redhat dot com 2004-07-08 16:27 -------
Subject: Re: New c-torture failures after
bitfield patch
On Thu, 2004-07-08 at 11:57, jsm at polyomino dot org dot uk wrote:
> struct tmp
> {
> long long int pad : 12;
> long long int field : 52;
> };
>
> main()
> {
> struct tmp tmp = {0x123, 0xFFF000FFF000FLL};
>
> if (tmp.field != 0xFFFFFF000FFF000FLL)
> abort();
>
> exit (0);
> }
>
> from my previous message also fail now? If so, that should speed up
> investigating this one. If not, I'll start from the full bf64-1.c.
>
This one works. We don't fold the conditional into 'if (1)' like we do
in the full test. Perhaps a good starting point is to set a breakpoint
in gimplify_cond_expr and follow the path into some call to fold().
Diego.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16437