All of lore.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: Re: gcc-3.3.1-hammer breaks mm/memory.c
Date: Wed, 16 Jul 2003 02:05:32 +0200	[thread overview]
Message-ID: <20030716000532.GC2447@werewolf.able.es> (raw)
In-Reply-To: 20030715222701.GC3823@werewolf.able.es


On 07.16, J.A. Magallon wrote:
> Hi all...
> 
> After some binary search and a 'couple' kernel builds, I narrowed the
> problem to mm/memory.c. With that file built at -O1:
> 
> CFLAGS_memory.o = -O1
> 
> The kernel boots, starts /sbin/init and looks like working normally
> (2.4.22-pre5).
> 
> Anybody can see what is miscompiled with an assembler listing ?
> Any #pragma to switch optmizations on the half of a file or for
> a function ?
> 

I finally got this: -O2 fails but

CFLAGS_memory.o = -Os -falign-functions -falign-jumps -falign-loops -falign-labels -fprefetch-loop-arrays -freorder-blocks

works.

Those are specific options disabled by -Os, but -Os does more things...
(assembler output is very different)

Any SuSE site (hammer comes from SuSE, isn't it ?) to submit a decent
bug report ?

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-pre5-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-0.2mdk))

  reply	other threads:[~2003-07-15 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 22:27 gcc-3.3.1-hammer breaks mm/memory.c J.A. Magallon
2003-07-16  0:05 ` J.A. Magallon [this message]
2003-07-16  1:50   ` Andrea Arcangeli

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=20030716000532.GC2447@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.