public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Josh McKinney <forming@home.com>
To: gcc@gcc.gnu.org
Subject: Re: compiling linux kernels with GCC 3.0
Date: Wed, 10 Oct 2001 09:04:00 -0000	[thread overview]
Message-ID: <20011010110411.A6108@cy599856-a.home.com> (raw)
In-Reply-To: <87669nimpr.fsf@deneb.enyo.de>

 Alan Lehotsky <apl@alum.mit.edu> writes:
 
> > Is it still the case that standard 3.0.x compilers are unable to
> > compile current linux kernels due to mismatched expectations on
> > optimizations?

The most recent snapshot compiles great for me.  I had some problems in that
past with k6 optimizations and alignment, but now it has been working great.

Josh
-- 
Linux, the choice                | It's always darkest just before it gets
of a GNU generation       -o)    | pitch black. 
Kernel 2.4.10-ac10         /\    | 
on a i586                 _\_v   | 
                                 | 

  reply	other threads:[~2001-10-10  9:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10  5:37 Alan Lehotsky
2001-10-10  7:22 ` Florian Weimer
2001-10-10  9:04   ` Josh McKinney [this message]
2001-10-10  9:26 ` Linus Torvalds
2001-10-10 11:09   ` Joe Buck
2001-10-10 11:23     ` Linus Torvalds
2001-10-10 15:23       ` Joe Buck
2001-10-10 16:19         ` Paolo Carlini
2001-10-10 16:58           ` Richard Henderson
2001-10-10 17:09             ` Paolo Carlini
2001-10-10 17:12               ` Richard Henderson
2001-10-10 19:03               ` Tim Prince
2001-10-10 15:39       ` Matthew Woodcraft
2001-10-10 11:40   ` Mark Mitchell
2001-10-10 14:01     ` Paolo Carlini
2001-10-10 14:15       ` Mark Mitchell
2001-10-10 14:54         ` Paolo Carlini
2001-10-10 15:57       ` Joe Buck
2001-10-10 11:23 Reichelt

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=20011010110411.A6108@cy599856-a.home.com \
    --to=forming@home.com \
    --cc=gcc@gcc.gnu.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).