From: David Edelsohn <dje@watson.ibm.com>
To: Daniel Berlin <dberlin@dberlin.org>,
Toon Moene <toon@moene.indiv.nluug.nl>
Cc: gcc@gcc.gnu.org
Subject: Re: Alias analysis - does base_alias_check still work ?
Date: Fri, 19 Jul 2002 11:03:00 -0000 [thread overview]
Message-ID: <200207191454.KAA27500@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Daniel Berlin <dberlin@dberlin.org> of "Fri, 19 Jul 2002 10:51:59 EDT." <Pine.LNX.4.44.0207191051100.18232-100000@dberlin.org>
>>>>> Daniel Berlin writes:
>> Which begs the question: Is there a reason -fschedule-insns isn't on by
>> default when using -O2 ?
Daniel> Err, it is.
Daniel> if (optimize >= 2)
Daniel> flag_peephole2 = 1;
Daniel> #ifdef INSN_SCHEDULING
Daniel> flag_schedule_insns = 1;
Daniel> flag_schedule_insns_after_reload = 1;
Daniel> #endif
Except i386.c turns it off:
void
optimization_options (level, size)
int level;
int size ATTRIBUTE_UNUSED;
{
/* For -O2 and beyond, turn off -fschedule-insns by default. It tends to
make the problem with not enough registers even worse. */
#ifdef INSN_SCHEDULING
if (level > 1)
flag_schedule_insns = 0;
#endif
David
next prev parent reply other threads:[~2002-07-19 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 14:10 Toon Moene
2002-07-19 11:00 ` Toon Moene
2002-07-19 11:02 ` Daniel Berlin
2002-07-19 11:03 ` David Edelsohn [this message]
2002-07-19 13:31 ` Richard Henderson
2002-07-20 2:13 ` Toon Moene
2002-07-20 11:42 ` Toon Moene
2002-07-20 12:05 ` Richard Henderson
2002-07-20 12:12 ` Richard Henderson
2002-07-21 10:01 ` Toon Moene
2002-07-21 14:23 ` Richard Henderson
2002-07-21 15:14 ` Toon Moene
2002-07-21 22:41 ` Toon Moene
2002-07-22 0:03 ` Richard Henderson
2002-07-22 16:42 ` Toon Moene
2002-07-23 2:12 ` Andreas Jaeger
2002-08-12 7:49 ` Jeff Law
2002-08-12 7:53 ` Jan Hubicka
2002-08-12 9:56 ` Richard Henderson
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=200207191454.KAA27500@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).