public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44945] New: [4.6 Regression] FAIL: gfortran.dg/char_array_structure_constructor.f90
Date: Thu, 15 Jul 2010 08:32:00 -0000 [thread overview]
Message-ID: <bug-44945-12313@http.gcc.gnu.org/bugzilla/> (raw)
At revision 162192, I get with -m32:
FAIL: gfortran.dg/char_array_structure_constructor.f90 -O3
-fomit-frame-pointer execution test
The failure is a "Bus error" with -O2 and -O3, and requires
-fomit-frame-pointer. Also the failure goes away when Revision 162148 was OK
and the test passes on powerpc-apple-darwin9 (r162194).
The backtrace is
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x000adddc in __gfortran_compare_string (len1=4, s1=0x0, len2=4, s2=0x1f40
"wxyzabcdefgh") at intrinsics/string_intrinsics_inc.c:93
93 res = memcmp (s1, s2, ((len1 < len2) ? len1 : len2) * sizeof
(CHARTYPE));
(gdb) bt
#0 0x000adddc in __gfortran_compare_string (len1=4, s1=0x0, len2=4, s2=0x1f40
"wxyzabcdefgh") at intrinsics/string_intrinsics_inc.c:93
#1 0x00001e31 in main ()
--
Summary: [4.6 Regression] FAIL:
gfortran.dg/char_array_structure_constructor.f90
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dominiq at lps dot ens dot fr
GCC build triplet: x86_64-apple-darwin10
GCC host triplet: x86_64-apple-darwin10
GCC target triplet: x86_64-apple-darwin10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44945
next reply other threads:[~2010-07-15 8:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 8:32 dominiq at lps dot ens dot fr [this message]
2010-07-15 8:39 ` [Bug middle-end/44945] " rguenth at gcc dot gnu dot org
2010-07-15 14:38 ` [Bug fortran/44945] " burnus at gcc dot gnu dot org
2010-07-15 15:23 ` dominiq at lps dot ens dot fr
2010-07-15 15:24 ` dominiq at lps dot ens dot fr
2010-07-15 15:27 ` dominiq at lps dot ens dot fr
2010-07-15 16:02 ` [Bug middle-end/44945] " burnus at gcc dot gnu dot org
2010-07-15 16:25 ` dominiq at lps dot ens dot fr
2010-07-15 18:56 ` dominiq at lps dot ens dot fr
2010-07-15 20:20 ` jakub at gcc dot gnu dot org
2010-07-16 8:39 ` [Bug fortran/44945] " rguenth at gcc dot gnu dot org
2010-07-16 8:51 ` dominiq at lps dot ens dot fr
2010-07-16 9:12 ` [Bug fortran/44945] [4.6 Regression] Wrong decl for module vars / " burnus at gcc dot gnu dot org
2010-07-16 10:08 ` jakub at gcc dot gnu dot org
2010-07-16 12:08 ` burnus at gcc dot gnu dot org
2010-07-16 12:09 ` burnus at gcc dot gnu dot org
2010-07-16 12:33 ` jakub at gcc dot gnu dot org
2010-07-16 14:22 ` burnus at gcc dot gnu dot org
2010-07-16 14:38 ` paul dot richard dot thomas at gmail dot com
2010-07-16 14:47 ` burnus at gcc dot gnu dot org
2010-07-23 20:13 ` burnus at gcc dot gnu dot org
2010-07-23 20:16 ` burnus at gcc dot gnu dot org
2010-07-24 5:38 ` dominiq at lps dot ens dot fr
2010-07-24 6:52 ` burnus at gcc dot gnu dot org
2010-07-24 7:50 ` dominiq at lps dot ens dot fr
2010-07-24 13:44 ` rguenther at suse dot de
2010-07-24 18:14 ` burnus at gcc dot gnu dot org
2010-07-28 7:41 ` burnus at gcc dot gnu dot org
2010-08-17 9:42 ` pault at gcc dot gnu dot org
2010-08-18 14:41 ` mikael at gcc dot gnu dot org
2010-09-21 13:16 ` rguenth 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=bug-44945-12313@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).