From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc-3.2 bug
Date: Wed, 05 Mar 2003 02:03:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805970@msgid-missing> (raw)
>>>>> On Tue, 28 Jan 2003 14:58:28 -0700, Alex Williamson <alex_williamson@hp.com> said:
Alex> I've been trying to figure out why agpgart_be.c won't
Alex> compile on ia64 w/ gcc-3.2, and I've got a pretty simple test
Alex> case that seems to show a compiler bug. Not being much of a
Alex> tools guy, I figured I'd toss it out here. If I compile with
Alex> -O2, I get an undefined reference much like I see in the
Alex> kernel:
Alex> # gcc -O2 -o test test.c /tmp/ccQCPFMM.o(.text+0xa0): In
Alex> function `main': : undefined reference to `.L13' collect2: ld
Alex> returned 1 exit status
Alex> If I compile w/o optimization or w/ gcc-2.96, it works fine.
Alex> It also works fine on x86 w/ gcc-3.2. Here's my gcc info:
Hans tried this with gcc-3.3 and the latest CVS gcc and both worked
fine (I was able to reproduce the bug with 3.2.2). Looks like the
problem might have been fixed already.
--david
next reply other threads:[~2003-03-05 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 2:03 David Mosberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 21:58 [Linux-ia64] gcc-3.2 bug Alex Williamson
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=marc-linux-ia64-105590709805970@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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