public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61138] [4.8/4.9/4.10 Regression] Wrong code with pointer-bounds remapping
Date: Sat, 10 May 2014 09:13:00 -0000	[thread overview]
Message-ID: <bug-61138-4-W3xzxyYdlp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61138-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-05-10
            Summary|Wrong code with             |[4.8/4.9/4.10 Regression]
                   |pointer-bounds remapping    |Wrong code with
                   |                            |pointer-bounds remapping
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
r190619 (2012-08-23) is OK, r190641 (2012-08-24) miscompiles the test. Likely
r190641.


  reply	other threads:[~2014-05-10  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10  8:30 [Bug fortran/61138] New: " burnus at gcc dot gnu.org
2014-05-10  9:13 ` dominiq at lps dot ens.fr [this message]
2014-05-13  9:55 ` [Bug fortran/61138] [4.8/4.9/4.10 Regression] " rguenth at gcc dot gnu.org
2014-05-22  9:06 ` rguenth at gcc dot gnu.org
2014-05-25 12:28 ` mikael at gcc dot gnu.org
2014-12-19 13:34 ` [Bug fortran/61138] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-06 21:00 ` mikael at gcc dot gnu.org
2015-02-09 12:57 ` mikael at gcc dot gnu.org
2015-03-14 12:24 ` mikael at gcc dot gnu.org
2015-03-21 15:47 ` mikael at gcc dot gnu.org
2015-03-21 18:16 ` mikael at gcc dot gnu.org
2015-03-21 18:20 ` mikael 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-61138-4-W3xzxyYdlp@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).