public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44660] [regression 4.4/4.5/4.6] ICE in resolve_equivalence()
Date: Fri, 25 Jun 2010 17:15:00 -0000 [thread overview]
Message-ID: <20100625171442.7507.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44660-7780@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from kargl at gcc dot gnu dot org 2010-06-25 17:14 -------
(In reply to comment #11)
>
> Well, it is invalid code - based on a valid Fortran code. If you use Delta to
> reduce a test case (cf. http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction),
> it simply removes lines of the source code using a constraint. I think
> Sebastian's constraint was that it segfaults. This seemingly happens for the
> unmodified gamess due to a Graphite bug - but also due to a buggy error
> recovery in gfortran.
Well, then Delta is broken for fortran. Reducing valid fortran that is
causing a compiler issue to some invalid fortran fragment that may or
(more than likely) may not have anything to do with the original issue
is a waste of time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44660
next prev parent reply other threads:[~2010-06-25 17:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 2:37 [Bug fortran/44660] New: " spop at gcc dot gnu dot org
2010-06-25 4:02 ` [Bug fortran/44660] [regression 4.4/4.5/4.6] " kargl at gcc dot gnu dot org
2010-06-25 4:35 ` jvdelisle at gcc dot gnu dot org
2010-06-25 4:42 ` kargl at gcc dot gnu dot org
2010-06-25 5:33 ` sebpop at gmail dot com
2010-06-25 5:49 ` sebpop at gmail dot com
2010-06-25 6:07 ` Sebastian Pop
2010-06-25 6:08 ` sebpop at gmail dot com
2010-06-25 6:14 ` kargl at gcc dot gnu dot org
2010-06-25 6:20 ` burnus at gcc dot gnu dot org
2010-06-25 6:24 ` sebpop at gmail dot com
2010-06-25 6:30 ` kargl at gcc dot gnu dot org
2010-06-25 9:17 ` burnus at gcc dot gnu dot org
2010-06-25 10:32 ` mikael at gcc dot gnu dot org
2010-06-25 10:33 ` mikael at gcc dot gnu dot org
2010-06-25 17:15 ` kargl at gcc dot gnu dot org [this message]
2010-06-25 18:12 ` jakub at gcc dot gnu dot org
2010-07-22 9:44 ` burnus at gcc dot gnu dot org
2010-07-23 3:05 ` jvdelisle at gcc dot gnu dot org
2010-07-24 19:52 ` mikael at gcc dot gnu dot org
2010-07-25 17:01 ` mikael at gcc dot gnu dot org
2010-07-27 12:07 ` [Bug fortran/44660] [regression 4.4/4.5] " mikael at gcc dot gnu dot org
2010-08-05 21:39 ` [Bug fortran/44660] [4.4/4.5 Regression] " mikael at gcc dot gnu dot org
2010-08-05 21:40 ` [Bug fortran/44660] [4.4 " mikael at gcc dot gnu dot org
2010-08-06 17:18 ` mikael at gcc dot gnu dot org
2010-08-06 17:19 ` [Bug fortran/44660] " mikael 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=20100625171442.7507.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: 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).