public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/42479] Wrong code with -floop-block Date: Tue, 05 Jan 2010 11:42:00 -0000 [thread overview] Message-ID: <20100105114249.20966.qmail@sourceware.org> (raw) In-Reply-To: <bug-42479-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from fxcoudert at gcc dot gnu dot org 2010-01-05 11:42 ------- Created an attachment (id=19471) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19471&action=view) Source file and input file Compile induct.f90 and run with induct.in in the same directory. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42479
next prev parent reply other threads:[~2010-01-05 11:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-23 13:54 [Bug middle-end/42479] New: Wrong-code for induct.f90 with " -O3 -floop-block" dominiq at lps dot ens dot fr 2010-01-05 11:41 ` [Bug middle-end/42479] Wrong code with -floop-block fxcoudert at gcc dot gnu dot org 2010-01-05 11:42 ` fxcoudert at gcc dot gnu dot org [this message] 2010-01-05 12:56 ` dominiq at lps dot ens dot fr 2010-01-05 14:35 ` dominiq at lps dot ens dot fr 2010-01-06 19:20 ` dominiq at lps dot ens dot fr 2010-01-07 22:36 ` [Bug middle-end/42479] [graphite] " spop at gcc dot gnu dot org 2010-01-14 8:41 ` spop at gcc dot gnu dot org 2010-02-06 16:33 ` spop at gcc dot gnu dot org
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=20100105114249.20966.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).