public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64757] internal compiler error: in fold_convert_loc, at fold-const.c:2353
Date: Sat, 24 Jan 2015 12:20:00 -0000 [thread overview]
Message-ID: <bug-64757-4-1DKSURHPBR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64757-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64757
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|RESOLVED |NEW
Last reconfirmed| |2015-01-24
CC| |janus at gcc dot gnu.org
Resolution|DUPLICATE |---
Ever confirmed|0 |1
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #1
> Thus I think it is a duplicate of pr49213.
It it certainly related, but I'm not sure it is an exact duplicate. In
particular the above PR has quite a history and includes several test cases.
Let's keep it separate for now.
next prev parent reply other threads:[~2015-01-24 12:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 22:34 [Bug fortran/64757] New: " mike at rilee dot net
2015-01-24 11:52 ` [Bug fortran/64757] " dominiq at lps dot ens.fr
2015-01-24 12:20 ` janus at gcc dot gnu.org [this message]
2015-01-24 12:24 ` [Bug fortran/64757] [5 Regression] ICE " janus at gcc dot gnu.org
2015-01-24 12:31 ` dominiq at lps dot ens.fr
2015-01-24 12:35 ` janus at gcc dot gnu.org
2015-01-24 22:25 ` janus at gcc dot gnu.org
2015-01-26 11:33 ` rguenth at gcc dot gnu.org
2015-01-28 13:37 ` pault at gcc dot gnu.org
2015-01-28 14:42 ` pault at gcc dot gnu.org
2015-01-28 16:19 ` dominiq at lps dot ens.fr
2015-02-05 8:06 ` pault at gcc dot gnu.org
2015-02-05 8:09 ` pault at gcc dot gnu.org
2015-02-05 8:45 ` burnus 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-64757-4-1DKSURHPBR@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).