From: Jeff Mahoney <jeffm@suse.de>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org, reiserfs-dev@namesys.com
Subject: Re: [PATCH] make gcc -O1 in fs/reiserfs optional
Date: Tue, 26 Apr 2005 17:46:00 -0400 [thread overview]
Message-ID: <426EB698.9030108@suse.de> (raw)
In-Reply-To: <20050426211019.GA11579@suse.de>
Olaf Hering wrote:
> Jeff,
>
> you added this EXTRA_CFLAGS= during 2.4 development, I think the broken
> compiler was gcc 3.2 on SLES8. Can we turn this -O1 into a .config
> option?
Hi Olaf -
Yeah, the initial problem was that the anti aliasing[*] code when -O2
was enabled was being way too cautious and ended up allocating something
like 6k on the stack in do_balance(). It was observable elsewhere, but
not so problematic.
My ppc box isn't booting right now. If you've verified that newer
versions of the compiler don't blow the stack in do_balance(), I'm not
opposed to it.
-Jeff
[*]: I think that's the right term - I'm not a compiler developer :)
--
Jeff Mahoney
SuSE Labs
next prev parent reply other threads:[~2005-04-26 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 21:10 [PATCH] make gcc -O1 in fs/reiserfs optional Olaf Hering
2005-04-26 21:46 ` Jeff Mahoney [this message]
2005-04-27 13:40 ` Hans Reiser
2005-10-11 19:01 ` Olaf Hering
2005-10-11 20:04 ` Hans Reiser
2005-10-13 23:27 ` Andrew Morton
2005-10-14 1:17 ` Jeff Mahoney
2006-07-24 6:52 ` [PATCH] use gcc -O1 in fs/reiserfs only for ancient gcc versions Olaf Hering
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=426EB698.9030108@suse.de \
--to=jeffm@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
--cc=reiserfs-dev@namesys.com \
/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 NNTP newsgroup(s).