From: Chris Meadors <twrchris@hereintown.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make gcc3.3 Eliminate Unused Static Functions
Date: Thu, 19 Jun 2003 10:32:24 -0400 [thread overview]
Message-ID: <3EF1C978.6050502@hereintown.net> (raw)
In-Reply-To: <20030619135800.6D4514F01@gherkin.frus.com>
Bob Tracy wrote:
> Another data point... Earlier (I *think* it was this thread) someone
> mentioned problems with trying to build glibc with gcc 3.x and "ls"
> segfaulting. I've recently upgraded portions of my system (including
> libraries and compilers) with the packages from the Slackware 9.0 CD.
> I expect a certain amount of pain (due to library version conflicts)
> every time I go through the upgrade process, but this time the pain
> feels different... I absolutely cannot get getty and uugetty from the
> getty-ps-2.1.0 package to work: segmentation faults. Even tried building
> from source: no good. My old getty and uugetty binaries (version 2.0.7j)
> seem to work ok with the new libraries, but rebuilding the 2.0.7j code
> with gcc-3.2.2 results in segfaults.
That was me, but it wasn't this thread. I was talking about building
glibc against the 2.5.x kernel headers, that caused problems. glibc
2.3.2 with gcc 3.3 against the 2.4.20 headers is perfectly stable, and
passes all tests in "make check". Even with "-O3 -march=athlon-xp
-mfpmath=sse", the only tests that fail are in the trig functions (SSE
on the Althon only has 32 bit precision so the values are truncated).
--
Chris
next prev parent reply other threads:[~2003-06-19 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:17 [PATCH] Make gcc3.3 Eliminate Unused Static Functions Rusty Russell
2003-06-13 3:01 ` Bernd Eckenfels
2003-06-13 14:04 ` Chris Friesen
2003-06-13 16:03 ` Tom Rini
2003-06-13 18:07 ` Robert Love
2003-06-13 18:15 ` Tom Rini
2003-06-13 18:41 ` Robert Love
2003-06-19 12:10 ` Adrian Bunk
2003-06-19 13:28 ` Jörn Engel
2003-06-19 13:57 ` Bob Tracy
2003-06-19 14:32 ` Chris Meadors [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 1:03 Rusty Russell
2003-06-19 12:17 ` Adrian Bunk
2003-06-20 2:28 ` Rusty Russell
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=3EF1C978.6050502@hereintown.net \
--to=twrchris@hereintown.net \
--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