From: John Heil <kerndev@sc-software.com>
To: linux-kernel@vger.kernel.org
Subject: Is gcc 3.2.2 suitable for kernel builds?
Date: Mon, 26 Jan 2004 22:15:29 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401262211480.7728@scsoftware.sc-software.com> (raw)
It seems that some gcc 3.2.2 optimizations are generating
bogus code sequences.
Has anyone else had compiler issues w gcc 3.2.2?
Thanks much,
johnh
-
-----------------------------------------------------------------
John Heil
South Coast Software
Custom systems software for UNIX and IBM MVS mainframes
1-714-774-6952
johnhscs@sc-software.com
http://www.sc-software.com
-----------------------------------------------------------------
next reply other threads:[~2004-01-27 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 6:15 John Heil [this message]
2004-01-27 10:19 ` m0sia
2004-01-27 10:37 ` Daniel Andersen
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=Pine.LNX.4.58.0401262211480.7728@scsoftware.sc-software.com \
--to=kerndev@sc-software.com \
--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
Powered by JetHome