This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Instruction scheduler bug (?) in gcc-2.95.2
- To: "Weininger, Nicholas (MN65)" <weininger_nicholas at htc dot honeywell dot com>
- Subject: Re: Instruction scheduler bug (?) in gcc-2.95.2
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Fri, 23 Jun 2000 08:27:52 -0600
- cc: "'gcc-bugs at gcc dot gnu dot org'" <gcc-bugs at gcc dot gnu dot org>
- Reply-To: law at cygnus dot com
In message <D1727A94A90CD411B96700805F158E794D7463@mn65-blazer.htc.honeywell.
com>you write:
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
>
> ------_=_NextPart_000_01BFDC8D.1ABAEA60
> Content-Type: text/plain;
> charset="iso-8859-1"
>
> When I invoke gcc 2.95.2 on the attached preprocessed file, with the option
> s
> shown below, I get the error output shown below.
> As there are no asm directives in the preprocessed file, I believe this to
> be a compiler bug.
> The error output does not occur if I compile with -O1 alone, or with -O2 or
> -O3 alone-- only if I combine -O1 and -fschedule-insns; thus the hypothesis
> about the bug in the subject line.
You can't use -fschedule-insns on the ia32. Sorry.
You can use -fschedule-insns2, which is safe for the ia32 port.
jeff