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 rtl-optimization/64921] [4.9/5 Regression] FAIL: gfortran.dg/class_allocate_18.f90
Date: Wed, 04 Feb 2015 19:00:00 -0000 [thread overview]
Message-ID: <bug-64921-4-eMc0pd668m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64921-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64921
--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> If I have understood correctly, -fPIC is not supported on x86_64 and so,
> unless I am mistaken, I cannot help you further.
This is not how I understand comment 1.
Note that if I compile with -fsanitize=address, the executable crashes with
allocated!
=================================================================
==73209==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x60200000e040 at pc 0x000103b59dbd bp 0x7fff5c0a6fa0 sp 0x7fff5c0a6f98
READ of size 8 at 0x60200000e040 thread T0
#0 0x103b59dbc
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001dbc)
#1 0x103b595aa
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x1000015aa)
#2 0x103b59889
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001889)
#3 0x103b5a7a6
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x1000027a6)
#4 0x7fff8fd1e5c8 (/usr/lib/system/libdyld.dylib+0x35c8)
#5 0x0 (<unknown module>)
0x60200000e040 is located 0 bytes to the right of 16-byte region
[0x60200000e030,0x60200000e040)
allocated by thread T0 here:
#0 0x103b8d1fa (/opt/gcc/gcc4.10w/lib/libasan.2.dylib+0x2f1fa)
#1 0x103b59642
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100001642)
#2 0x103b5a7a6
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x1000027a6)
#3 0x7fff8fd1e5c8 (/usr/lib/system/libdyld.dylib+0x35c8)
#4 0x0 (<unknown module>)
SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 ??
Shadow bytes around the buggy address:
0x1c0400001bb0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001be0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x1c0400001bf0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa 01 fa
=>0x1c0400001c00: fa fa 00 fa fa fa 00 00[fa]fa 07 fa fa fa 07 fa
0x1c0400001c10: fa fa 06 fa fa fa 00 06 fa fa 00 00 fa fa 03 fa
0x1c0400001c20: fa fa 00 06 fa fa 00 07 fa fa 00 fa fa fa 00 00
0x1c0400001c30: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
0x1c0400001c40: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
0x1c0400001c50: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00
I see this for r220302, r220156, r220109, and r219830 (i.e., all the revisions
I have tested).
Note that Janus has removed the -fsanitize=undefined option at r220181, while
it worked for me provided I ran the test after install.
next prev parent reply other threads:[~2015-02-04 19:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 15:42 [Bug rtl-optimization/64921] New: [5 Regression] FAIL: gfortran.dg/class_allocate_18.f90 with -fPIC hjl.tools at gmail dot com
2015-02-03 16:03 ` [Bug rtl-optimization/64921] " jakub at gcc dot gnu.org
2015-02-03 17:22 ` hjl.tools at gmail dot com
2015-02-03 17:32 ` [Bug rtl-optimization/64921] [4.9/5 Regression] FAIL: gfortran.dg/class_allocate_18.f90 hjl.tools at gmail dot com
2015-02-03 21:30 ` pault at gcc dot gnu.org
2015-02-04 3:00 ` ramana at gcc dot gnu.org
2015-02-04 18:21 ` pault at gcc dot gnu.org
2015-02-04 18:31 ` hjl.tools at gmail dot com
2015-02-04 19:00 ` dominiq at lps dot ens.fr [this message]
2015-02-04 19:03 ` dominiq at lps dot ens.fr
2015-02-09 0:07 ` pinskia at gcc dot gnu.org
2015-02-09 10:00 ` rguenth at gcc dot gnu.org
2015-02-09 14:26 ` rguenth at gcc dot gnu.org
2015-02-16 13:40 ` dominiq at lps dot ens.fr
2015-02-16 13:48 ` [Bug fortran/64921] " dominiq at lps dot ens.fr
2015-04-27 12:26 ` [Bug fortran/64921] [4.9/5/6 " mathewc at nag dot co.uk
2015-06-26 20:04 ` jakub at gcc dot gnu.org
2015-06-26 20:34 ` jakub at gcc dot gnu.org
2015-07-07 15:29 ` ktkachov at gcc dot gnu.org
2015-07-25 13:31 ` ubizjak at gmail dot com
2015-07-25 15:13 ` ubizjak at gmail dot com
2015-07-27 7:57 ` rguenth at gcc dot gnu.org
2015-07-27 18:45 ` mikael at gcc dot gnu.org
2015-07-27 19:44 ` rguenther at suse dot de
2015-07-28 12:07 ` mikael at gcc dot gnu.org
2015-07-28 12:31 ` rguenther at suse dot de
2015-07-28 12:43 ` ubizjak at gmail dot com
2015-08-05 15:42 ` mikael at gcc dot gnu.org
2015-08-05 16:42 ` mikael at gcc dot gnu.org
2015-08-05 17:04 ` mikael 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-64921-4-eMc0pd668m@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).