public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philipp Thomas <pthomas@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10225: Unnamed structs aren't handled correctly in 3.3
Date: Wed, 26 Mar 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030326173600.21776.qmail@sources.redhat.com> (raw)

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

From: Philipp Thomas <pthomas@suse.de>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, aj@suse.de
Subject: Re: c/10225: Unnamed structs aren't handled correctly in 3.3
Date: Wed, 26 Mar 2003 18:33:47 +0100

 * Steven Bosscher (s.bosscher@student.tudelft.nl) [20030326 18:25]:
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10225
 > 
 > Hmm...  Didn't work with 2.95.3 apparently, so the
 > kernel had better not rely on this "feature".
 
 The code takes into account that gcc 2.95.3 doesn't support this. But seeing
 the extra macro stuff that generates the correct member names depending on
 the compiler used (e.g. you have to use ie->_IIF(iff,length) makes me really
 wonder why they even use the stuff .....
 
 Philipp
 
 -- 
 Philipp Thomas <pthomas@suse.de>
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nuremberg, Germany


             reply	other threads:[~2003-03-26 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 17:46 Philipp Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 17:27 Steven Bosscher
2003-03-26 17:16 pthomas

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=20030326173600.21776.qmail@sources.redhat.com \
    --to=pthomas@suse.de \
    --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).