public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49103] [4.6/4.7 Regression] local variables exchange values / wrong code with -O3
Date: Tue, 31 May 2011 13:40:00 -0000	[thread overview]
Message-ID: <bug-49103-4-okBrQlFxWy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49103-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49103

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-31 13:28:17 UTC ---
Created attachment 24402
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24402
gcc46-pr49103.patch

While micha's patch is the way to go for the trunk, it most likely isn't
backportable.
This untested hack is an attempt to avoid reverting my patch if the vars aren't
stored in bbs with significant code motion.  If anyone has better place to
set the bit, I'd appreciate it.


  parent reply	other threads:[~2011-05-31 13:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 17:54 [Bug fortran/49103] New: " thomas.orgis at awi dot de
2011-05-21 18:50 ` [Bug fortran/49103] " dominiq at lps dot ens.fr
2011-05-21 21:37 ` [Bug fortran/49103] [4.6/4.7 Regression] " dominiq at lps dot ens.fr
2011-05-21 22:07 ` dominiq at lps dot ens.fr
2011-05-21 23:29 ` dominiq at lps dot ens.fr
2011-05-22 11:12 ` rguenth at gcc dot gnu.org
2011-05-22 11:22 ` dominiq at lps dot ens.fr
2011-05-23  7:59 ` jakub at gcc dot gnu.org
2011-05-28 11:28 ` dominiq at lps dot ens.fr
2011-05-28 11:29 ` burnus at gcc dot gnu.org
2011-05-28 18:05 ` dominiq at lps dot ens.fr
2011-05-31 11:59 ` jakub at gcc dot gnu.org
2011-05-31 13:40 ` jakub at gcc dot gnu.org [this message]
2011-06-12 13:44 ` rguenth at gcc dot gnu.org
2011-06-13  8:43 ` burnus at gcc dot gnu.org
2011-06-14 15:27 ` jakub at gcc dot gnu.org
2011-06-14 15:29 ` jakub at gcc dot gnu.org
2011-06-14 22:17 ` jakub at gcc dot gnu.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=bug-49103-4-okBrQlFxWy@http.gcc.gnu.org/bugzilla/ \
    --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: 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).