From: Andrea Arcangeli <andrea@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: gcc-3.3.1-hammer breaks mm/memory.c
Date: Wed, 16 Jul 2003 03:50:01 +0200 [thread overview]
Message-ID: <20030716015001.GA4978@dualathlon.random> (raw)
In-Reply-To: <20030716000532.GC2447@werewolf.able.es>
On Wed, Jul 16, 2003 at 02:05:32AM +0200, J.A. Magallon wrote:
>
> 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 ?
bugs@x86-64.org should be appropriate.
Andrea
prev parent reply other threads:[~2003-07-16 1:35 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
2003-07-16 1:50 ` Andrea Arcangeli [this message]
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=20030716015001.GA4978@dualathlon.random \
--to=andrea@suse.de \
--cc=jamagallon@able.es \
--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