From: rct@gherkin.frus.com (Bob Tracy)
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Tom Rini <trini@kernel.crashing.org>,
Chris Friesen <cfriesen@nortelnetworks.com>,
Bernd Eckenfels <ecki-lkm@lina.inka.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make gcc3.3 Eliminate Unused Static Functions
Date: Thu, 19 Jun 2003 08:57:59 -0500 (CDT) [thread overview]
Message-ID: <20030619135800.6D4514F01@gherkin.frus.com> (raw)
In-Reply-To: <20030619132810.GA6906@wohnheim.fh-wedel.de> =?ISO-8859-1?Q?from_J=F6rn_Engel_at_Jun_19=2C_2003_03=3A28=3A10_pm?=
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UNKNOWN-8BIT, Size: 1816 bytes --]
Jörn Engel wrote:
> I haven't seen a clear compiler bug yet, but found two bugs in
> assembler code with 2.95.3 that compiled without problems with 3.2.x.
> One of them has actually hit people, as you could see in the code.
> Most symptoms were "fixed", but the cause remained.
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.
The behavior seems to be independent of kernel version (2.5.70-2.5.72).
Here's the relevant version list (referenced libraries reported by ldd):
kernel 2.5.72
glibc 2.3.1
libtermcap 2.0.8
ld-2.3.1
gcc 3.2.2
binutils 2.13.90.0.18
The Slackware default install uses agetty rather than the getty-ps
package, which may partly explain why my particular symptom hasn't been
reported previously (to my knowledge). I'm curious to know if this
problem exists with a virgin Slackware 9 installation, and will probably
have an answer by this weekend, time permitting.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2003-06-19 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:17 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 [this message]
2003-06-19 14:32 ` Chris Meadors
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=20030619135800.6D4514F01@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=cfriesen@nortelnetworks.com \
--cc=ecki-lkm@lina.inka.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®