public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10826: [3.3/3.4 regression] Anonymous union regression
Date: Wed, 21 May 2003 01:46:00 -0000	[thread overview]
Message-ID: <20030521014600.23320.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10826; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
   bartoldeman@users.sourceforge.net, nobody@gcc.gnu.org, rth@redhat.com
Cc:  
Subject: Re: c/10826: [3.3/3.4 regression] Anonymous union regression
Date: Tue, 20 May 2003 18:35:22 -0700

 The test case starts getting an error with this patch:
 
 > 2002-06-16  Richard Henderson  <rth@redhat.com>
 >
 >       * c-common.c (flag_ms_extensions): Move from c++ front end.
 >       * c-common.h (flag_ms_extensions): Declare.
 >       * c-decl.c (c_decode_option): Add -fms-extensions.
 >       (grokfield): Don't accept anonymous structures in ISO C mode;
 >       accept only unnamed anonymous structures in GNU C mode; accept
 >       Plan 9 extensions in MS mode.
 >       * c-parse.in (SAVE_EXT_FLAGS, RESTORE_EXT_FLAGS): Rename from
 >       SAVE/RESTORE_WARN_FLAGS; add flag_iso frobbing; update all
 callers.
 >       (extension): Clear flag_iso.
 >       * doc/invoke.texi (C Dialect Options): Add -fms-extensions.
 >
 --- gcc/gcc/cp/ChangeLog ---
 > 2002-06-16  Richard Henderson  <rth@redhat.com>
 >
 >       * cp-tree.h, decl2.c (flag_ms_extensions): Move to c-common.
 
 It doesn't seem to be a regression after all, but a fix.
 
 Janis
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10826
 
 
 


             reply	other threads:[~2003-05-21  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21  1:46 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21 13:58 bangerth
2003-05-21  2:16 Richard Henderson
2003-05-16 20:39 bangerth

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=20030521014600.23320.qmail@sources.redhat.com \
    --to=janis187@us.ibm.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: link
Be 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).