mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Clayton Weaver <cgweav@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: broken gcc 3.x update ("3.4.3""fixed")
Date: Wed, 10 Nov 2004 10:07:23 +0000	[thread overview]
Message-ID: <20041110100723.GE24336@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20041110094011.0A3434BE64@ws1-1.us4.outblaze.com>

On Wed, Nov 10, 2004 at 04:40:10AM -0500, Clayton Weaver wrote:
> Apropos of the recent "older compilers" discussion,
> the string literal concatenation pre-processor bug
> that I mentioned encountering in gcc-3.3.x and
> gcc-3.4.[0,1] appears to be fixed in gcc-3.4.3.
> (It was not the well-known "##" token pasting
> pre-processor bug, incidentally.)
> 
> I've only tested with glibc-2.2.5 so far,
> but I could reproduce it before with both
> glibc-2.2.5 and glibc-2.3.2, so it probably
> really is fixed.

1) What the hell does glibc version have to preprocessor behaviour?
2) Could you post the code (as small as possible) that triggers whatever
bug you are talking about?  Not a "here's the fragment that gets miscompiled"
but something that could be fed to gcc and actually reproduce the bug.

  reply	other threads:[~2004-11-10 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10  9:40 Clayton Weaver
2004-11-10 10:07 ` Al Viro [this message]
2004-11-10 20:31   ` Bill Davidsen
2004-11-14  9:10 Clayton Weaver
2004-11-17 22:29 Clayton Weaver
2004-11-18  6:39 ` Willy Tarreau
2004-11-29  0:34 Clayton Weaver

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=20041110100723.GE24336@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=cgweav@email.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome