public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Date: Thu, 13 Feb 2003 21:56:00 -0000 [thread overview] Message-ID: <20030213215600.17098.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9052; it has been noted by GNATS. From: Eric Botcazou <ebotcazou@libertysurf.fr> To: Toon Moene <toon@moene.indiv.nluug.nl> Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>, Richard.Earnshaw@arm.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, phama@webjockey.net Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Date: Thu, 13 Feb 2003 22:41:43 +0100 > Exactly - however, I feel I cannot close these reports because I do not > have access to x86 hardware anymore, so I cannot easily test whether > they indeed *are* -ffloat-store issues .... Steven probably checked it too, but I can confirm that PR fortran/8445 vanishes (i.e the ouput is back to 1 line) when compiled with -O1 -ffloat-store instead of -O1 only. Reading specs from /usr/local/lib/gcc-lib/i586-redhat-linux-gnu/3.2.3/specs Configured with: ../configure --host=i586-redhat-linux-gnu --prefix=/usr/local --enable-languages=c,c++,objc,f77 --enable-checking=misc,tree --disable-nls Thread model: posix gcc version 3.2.3 20030210 (prerelease) -- Eric Botcazou
next reply other threads:[~2003-02-13 21:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-13 21:56 Eric Botcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-18 10:41 ebotcazou 2003-02-14 21:16 Toon Moene 2003-02-13 19:46 Toon Moene 2003-02-13 11:56 Eric Botcazou 2003-02-12 17:06 Steven Bosscher 2003-02-12 16:56 Eric Botcazou 2003-02-12 16:46 Richard Earnshaw 2003-02-12 16:36 Steven Bosscher 2003-02-12 16:26 Richard Earnshaw 2003-02-12 15:26 Steven Bosscher 2002-12-24 5:36 phma
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=20030213215600.17098.qmail@sources.redhat.com \ --to=ebotcazou@libertysurf.fr \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).