From: Joe Buck <jbuck@synopsys.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Rene Rebe <rene.rebe@gmx.net>,
rene@rocklinux.org, gcc@gcc.gnu.org,
libc-alpha@sources.redhat.com, rock-linux@rocklinux.org
Subject: Re: compiling glibc-2.3.1 with gcc-3.2.1 for pentium >= II
Date: Wed, 08 Jan 2003 22:05:00 -0000 [thread overview]
Message-ID: <20030108122814.A15747@synopsys.com> (raw)
In-Reply-To: <orlm1vo87h.fsf@free.redhat.lsd.ic.unicamp.br>; from aoliva@redhat.com on Wed, Jan 08, 2003 at 03:35:46PM -0200
On Jan 7, 2003, Rene Rebe <rene.rebe@gmx.net> wrote:
>
> > It is a gcc issue, since a Athlon optimised gcc-3.2.1 is able to
> > compile the same preprocessed file ...
... meaning that you should look at code that is #ifdefed out on the
Athlon. This *is* sysdep.h, after all.
On Wed, Jan 08, 2003 at 03:35:46PM -0200, Alexandre Oliva wrote:
> It's very unlikely to be a GCC issue. You're feeding GCC an assembly
> source file, and it's the assembler that is complaining about ignored
> characters. It could be a problem in the preprocessor, for sure, but
> then you'd have to save the preprocessed assembly generated by a
> working and broken preprocessor and compare them for the bug report to
> be useful.
Grep for __i686 in the input to GCC, then note that __i686 is a macro.
next prev parent reply other threads:[~2003-01-08 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 2:59 Rene Rebe
2003-01-08 5:27 ` Rene Rebe
2003-01-08 19:04 ` Alexandre Oliva
2003-01-08 22:05 ` Joe Buck [this message]
2003-01-09 0:48 ` Rene Rebe
2003-01-08 23:44 ` Richard Henderson
2003-01-08 18:36 ` Joe Buck
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=20030108122814.A15747@synopsys.com \
--to=jbuck@synopsys.com \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sources.redhat.com \
--cc=rene.rebe@gmx.net \
--cc=rene@rocklinux.org \
--cc=rock-linux@rocklinux.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).