public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49472] [gfortran, 4.7 regression] Compiler segfault on valid code
Date: Mon, 20 Jun 2011 11:31:00 -0000 [thread overview]
Message-ID: <bug-49472-4-B3NyIfDjmV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49472-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49472
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.06.20 11:31:25
Ever Confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-06-20 11:31:25 UTC ---
Revision 174379 is OK, 174487 is not. GDB shows
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00007fff5bc00ef8
0x000000010075c6f6 in simplify_binary_operation (code=MULT, mode=DFmode,
op0=0x141f29e10, op1=0x141f29438) at ../../work/gcc/simplify-rtx.c:1842
1842 && swap_commutative_operands_p (op0, op1))
next prev parent reply other threads:[~2011-06-20 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:05 [Bug fortran/49472] New: " martin@mpa-garching.mpg.de
2011-06-20 11:31 ` dominiq at lps dot ens.fr [this message]
2011-06-20 11:55 ` [Bug rtl-optimization/49472] [4.7 " rguenth at gcc dot gnu.org
2011-06-20 12:13 ` janus at gcc dot gnu.org
2011-06-20 14:13 ` dominiq at lps dot ens.fr
2011-06-20 14:18 ` dominiq at lps dot ens.fr
2011-06-20 15:18 ` wschmidt at gcc dot gnu.org
2011-06-20 15:19 ` wschmidt at gcc dot gnu.org
2011-06-20 16:09 ` jakub at gcc dot gnu.org
2011-06-21 7:52 ` jakub at gcc dot gnu.org
2011-06-21 8:33 ` ebotcazou at gcc dot gnu.org
2011-07-04 10:28 ` jakub at gcc dot gnu.org
2011-07-04 18:54 ` jakub at gcc dot gnu.org
2011-07-04 18:57 ` jakub at gcc dot gnu.org
2011-07-04 21:12 ` jakub 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-49472-4-B3NyIfDjmV@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).