mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "RaúlNúñez de Arenas Coronado" <raul@viadomus.com>
To: linux-kernel@vger.kernel.org, linux@sneulv.dk
Subject: Re: On K7, -march=k6 is good (Was Re: Why no -march=athlon?)
Date: Wed, 19 Dec 2001 21:33:14 +0100	[thread overview]
Message-ID: <E16GnOs-0000JT-00@DervishD.viadomus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

    Hello all :))

>> Is it safe to use gcc-3.0.2 to compile the kernel?
>If it compiles.. Otherwise use gcc-3.0.3(prerelease), it has fixes that makes 
>the _current_ kernel compile. 

    I've using gcc-3.0.1 to compile the kernel since it was released
and my linux 2.4.16 runs without problems. In my experience, the only
problem is the ICE raised by the 8139too driver, although this seems
to have been corrected on gcc-3.0.2 (I haven't updated my compiler
yet). I haven't found any bug yet running my linux box, but this
doesn't mean that gcc-3.0 is safe for the kernel. It's safe for my
configuration of the kernel, at least.

    Raúl

             reply	other threads:[~2001-12-19 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 20:33 RaúlNúñez de Arenas Coronado [this message]
2001-12-20  0:06 ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17 14:59 Why no -march=athlon? nbecker
2001-12-17 17:40 ` M. R. Brown
2001-12-19 17:46   ` On K7, -march=k6 is good (Was Re: Why no -march=athlon?) Benoit Poulot-Cazajous
2001-12-19 17:56     ` M. R. Brown
2001-12-19 18:39       ` nbecker
2001-12-19 18:47         ` M. R. Brown
2001-12-19 18:52           ` J Sloan
2001-12-19 19:01             ` Josh McKinney
2001-12-19 19:21             ` M. R. Brown
2001-12-19 19:28               ` J Sloan
2001-12-19 19:38         ` Allan Sandfeld
2001-12-19 21:40       ` Benoit Poulot-Cazajous

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=E16GnOs-0000JT-00@DervishD.viadomus.com \
    --to=raul@viadomus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@sneulv.dk \
    /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®