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/50070] Segmentation fault at size_binop_loc in fold-const.c
Date: Sat, 13 Aug 2011 12:06:00 -0000 [thread overview]
Message-ID: <bug-50070-4-UvK7QDe6xi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50070-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Known to fail| |4.1.2, 4.4.4, 4.5.4, 4.6.2,
| |4.7.0
--- Comment #2 from janus at gcc dot gnu.org 2011-08-13 11:53:58 UTC ---
(In reply to comment #1)
> I can confirm the segfault with 4.5, 4.6 and 4.7 (trunk) on the test case in
> comment #0:
Same with 4.4 and 4.1. Apparently this bug has been existing forever.
ifort rejects the original test case with:
error #6756: A COMMON block data object must not be an automatic object. [Z]
common n,z
-----------^
g95 says:
common n,z
1
Error: Character variable 'z' at (1) must have a constant length
I assume this is an ice-on-invalid-code.
next prev parent reply other threads:[~2011-08-13 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 7:12 [Bug fortran/50070] New: " zeccav at gmail dot com
2011-08-13 11:23 ` [Bug fortran/50070] " janus at gcc dot gnu.org
2011-08-13 12:06 ` janus at gcc dot gnu.org [this message]
2011-08-13 12:09 ` janus at gcc dot gnu.org
2011-08-14 12:08 ` janus at gcc dot gnu.org
2011-08-14 12:25 ` janus at gcc dot gnu.org
2011-08-14 13:21 ` janus at gcc dot gnu.org
2011-08-14 14:11 ` dominiq at lps dot ens.fr
2011-08-15 9:20 ` janus at gcc dot gnu.org
2011-08-15 9:53 ` janus at gcc dot gnu.org
2011-08-16 9:37 ` janus at gcc dot gnu.org
2011-08-17 9:26 ` janus at gcc dot gnu.org
2011-08-17 11:13 ` janus 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-50070-4-UvK7QDe6xi@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).