public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/8306: [3.2/3.3 regression] ICE for bitfield7_y.C in C++ compatibility tests Date: Sat, 15 Mar 2003 12:56:00 -0000 [thread overview] Message-ID: <20030315125601.28359.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/8306; it has been noted by GNATS. From: Richard Earnshaw <rearnsha@arm.com> To: Jason Merrill <jason@redhat.com> Cc: rearnsha@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, janis187@us.ibm.com Subject: Re: middle-end/8306: [3.2/3.3 regression] ICE for bitfield7_y.C in C++ compatibility tests Date: Sat, 15 Mar 2003 12:48:22 +0000 > On Fri, 31 Jan 2003 17:12:09 +0000, <rearnsha@gcc.gnu.org> wrote: > > > Correction, the "minimal example" no-longer fails, but the full testsuite > > entry does still fail. > > Does that still represent a regression? Mark said that previous compilers > would have just rejected such code. > > Jason Probably not. The 2.95.3 compiler I have gives: /work/rearnsha/gnusrc/gcc/gcc/testsuite/g++.dg/compat/break/bitfield7.h:3: sorry, not implemented: bit-fields larger than 64 bits In file included from /work/rearnsha/gnusrc/gcc/gcc/testsuite/g++.dg/compat /break/bitfield7_y.C:3: /work/rearnsha/gnusrc/gcc/gcc/testsuite/g++.dg/compat/break/bitfield7.h:2: in declaration of `U::i' I don't have 3.0 or 3.1 built to test against. R.
next reply other threads:[~2003-03-15 12:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-15 12:56 Richard Earnshaw [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-14 21:46 Jason Merrill 2003-01-31 17:16 rearnsha 2003-01-31 17:16 rearnsha
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030315125601.28359.qmail@sources.redhat.com \ --to=rearnsha@arm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).