public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: Andrea Arcangeli <andrea@suse.de>
Subject: gcc-3.3.1-hammer vs current pre
Date: Mon, 14 Jul 2003 01:40:24 +0200	[thread overview]
Message-ID: <20030713234024.GA2346@werewolf.able.es> (raw)

Hi all...

One good and one bad news...

The good:
Current 22-pre5 builds at -O1 level. I always thought it was mandatory to
build at -O2...At least it can be useful to detect optimizer bugs...

And the bad. The current gcc in mandrakke cooker miscompiles the kernel.
Current 2.4.22-pre5 (plain, even a comma touched) works if built with -O1
and breaks with -O2 (does not pass init launch). As it is based on
the hammer branch from SuSE, I think this also affects SuSE developers,
if not corrected in their tree yet.

Is there any way to set compile flags for _subsystems_ ? To start
a search on what breaks at -O2.

[OT] (off-topic, not Operacion Triunfo -bleh- ...)
BTW, is anybody from Mandrake reading this ? The cooker list looks dead
since a week or so. If someone reads this, plz mail me in private.

TIA

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.22-pre2-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-2mdk))

             reply	other threads:[~2003-07-13 23:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 23:40 J.A. Magallon [this message]
2003-07-14  0:43 ` gcc-3.3.1-hammer vs current pre Adrian Bunk

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=20030713234024.GA2346@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=andrea@suse.de \
    --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