All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Zaitsev <zzz@anda.ru>
To: Jim Wilson <wilson@specifixinc.com>
Cc: linux-gcc@vger.kernel.org, gcc@gcc.gnu.org
Subject: Re: GCC 3.3.2 -Wall affects the code generated...
Date: Wed, 7 Jul 2004 13:44:35 +0600	[thread overview]
Message-ID: <20040707134435.D17650@natasha.ward.six> (raw)
In-Reply-To: <1089159621.5679.174.camel@localhost>; from wilson@specifixinc.com on Tue, Jul 06, 2004 at 05:20:21PM -0700

On Tue, Jul 06, 2004 at 05:20:21PM -0700, Jim Wilson wrote:
> On Tue, 2004-07-06 at 15:46, Denis Zaitsev wrote:
> > I used to assume that everybody has the GLIBC tree.  :)
> 
> I have a glibc src/build tree on my IA-64 machine, but not on my x86
> machine.  I wasn't sure I'd get the right testcase if I tried to
> generate one on a IA-64 machine.  It seemed easier to ask you for one.

Ok.  I understand.

      reply	other threads:[~2004-07-07  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 18:03 GCC 3.3.2 -Wall affects the code generated Denis Zaitsev
2004-07-06 20:41 ` Jim Wilson
2004-07-06 21:11   ` John Richard Moser
2004-07-06 22:46   ` Denis Zaitsev
2004-07-07  0:20     ` Jim Wilson
2004-07-07  7:44       ` Denis Zaitsev [this message]

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=20040707134435.D17650@natasha.ward.six \
    --to=zzz@anda.ru \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-gcc@vger.kernel.org \
    --cc=wilson@specifixinc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.