public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61138] [4.8/4.9/5 Regression] Wrong code with pointer-bounds remapping
Date: Mon, 09 Feb 2015 12:57:00 -0000 [thread overview]
Message-ID: <bug-61138-4-AOtPW6rxbY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61138-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61138
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2015-02/msg00531.ht
| |ml
Assignee|unassigned at gcc dot gnu.org |mikael at gcc dot gnu.org
--- Comment #7 from Mikael Morin <mikael at gcc dot gnu.org> ---
Patch:
https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00531.html
next prev parent reply other threads:[~2015-02-09 12:57 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 ` [Bug fortran/61138] [4.8/4.9/4.10 Regression] " dominiq at lps dot ens.fr
2014-05-13 9:55 ` 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 [this message]
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-AOtPW6rxbY@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).