public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43227] [4.5/4.6 Regression] ICE: segmentation fault in mio_expr
Date: Mon, 19 Apr 2010 12:52:00 -0000 [thread overview]
Message-ID: <20100419125158.6012.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43227-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from janus at gcc dot gnu dot org 2010-04-19 12:51 -------
(In reply to comment #10)
> AFAICR the problem is specific to the fortran-dev branch.
No, this is definitely not the case! Only the failure of comment #0 is specific
to the branch. However, this failure is caused by an underlying problem with
procedure pointers, which is also present in the 4.5 release (see comment #3).
When searching for the origin of the regression, one should use the test case
in comment #3 and look at the 4.5 trunk.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43227
next prev parent reply other threads:[~2010-04-19 12:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 9:45 [Bug fortran/43227] New: [fortran-dev " dominiq at lps dot ens dot fr
2010-04-15 21:30 ` [Bug fortran/43227] " janus at gcc dot gnu dot org
2010-04-16 7:37 ` paul dot richard dot thomas at gmail dot com
2010-04-18 11:09 ` [Bug fortran/43227] [4.5 " janus at gcc dot gnu dot org
2010-04-18 11:49 ` [Bug fortran/43227] [4.5/4.6 " dominiq at lps dot ens dot fr
2010-04-18 16:19 ` dominiq at lps dot ens dot fr
2010-04-18 16:42 ` janus at gcc dot gnu dot org
2010-04-18 17:34 ` pault at gcc dot gnu dot org
2010-04-18 18:30 ` pault at gcc dot gnu dot org
2010-04-19 12:13 ` pault at gcc dot gnu dot org
2010-04-19 12:33 ` dominiq at lps dot ens dot fr
2010-04-19 12:52 ` janus at gcc dot gnu dot org [this message]
2010-04-19 13:07 ` dominiq at lps dot ens dot fr
2010-04-19 13:22 ` janus at gcc dot gnu dot org
2010-04-19 13:46 ` janus at gcc dot gnu dot org
2010-04-19 13:55 ` dominiq at lps dot ens dot fr
2010-04-19 15:13 ` burnus at gcc dot gnu dot org
2010-04-19 18:47 ` janus at gcc dot gnu dot org
2010-04-19 18:48 ` pault at gcc dot gnu dot org
2010-04-19 20:13 ` dominiq at lps dot ens dot fr
2010-04-19 21:16 ` pault at gcc dot gnu dot org
2010-04-19 21:34 ` janus at gcc dot gnu dot org
2010-04-20 5:00 ` pault at gcc dot gnu dot org
2010-04-20 6:19 ` pault at gcc dot gnu dot org
2010-04-20 9:18 ` dominiq at lps dot ens dot fr
2010-04-20 9:31 ` paul dot richard dot thomas at gmail dot com
2010-04-20 19:08 ` pault at gcc dot gnu dot org
2010-04-21 4:27 ` [Bug fortran/43227] [4.5 " pault at gcc dot gnu dot org
2010-04-24 12:30 ` pault at gcc dot gnu dot org
2010-04-24 12:31 ` pault 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=20100419125158.6012.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).