From: Serge Belyshev <33554432@mtu-net.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/i386/Makefile,scripts/gcc-version.sh,Makefile small fixes
Date: 25 Jan 2004 04:40:53 +0300 [thread overview]
Message-ID: <87hdykerfe.fsf@mtu-net.ru> (raw)
In-Reply-To: <20040124101704.3bf3ada2.akpm@osdl.org> (message from Andrew Morton on Sat, 24 Jan 2004 10:17:04 -0800)
>> * Consider adding -fweb option:
>
>What does it do?
>From gcc(1):
-fweb
Constructs webs as commonly used for register allocation purposes and
assign each web individual pseudo register. This allows our register
allocation pass to operate on pseudos directly, but also strengthens
several other optimization passes, such as CSE, loop optimizer and
trivial dead code remover. It can, however, make debugging impossible,
since variables will no longer stay in a ``home register''.
Enabled at levels -O3.
next prev parent reply other threads:[~2004-01-25 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 14:04 [PATCH] arch/i386/Makefile,scripts/gcc-version.sh,Makefile small fixes Serge Belyshev
2004-01-24 18:17 ` Andrew Morton
2004-01-24 18:32 ` Valdis.Kletnieks
2004-01-25 1:55 ` Serge Belyshev
2004-01-25 1:40 ` Serge Belyshev [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 14:37 sam
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=87hdykerfe.fsf@mtu-net.ru \
--to=33554432@mtu-net.ru \
--cc=akpm@osdl.org \
--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