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/65089] New: FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address
Date: Tue, 17 Feb 2015 10:07:00 -0000	[thread overview]
Message-ID: <bug-65089-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089

            Bug ID: 65089
           Summary: FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested
                    with -fsanitize=address
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dominiq at lps dot ens.fr

I have tested gfortran with

make -k check-gfortran
RUNTESTFLAGS="--target_board=unix'{-m32/-fsanitize=address,-m64/-fsanitize=address}'"

for 95 unexpected failures for -m32 or -m64 (well below what I anticipated!-).

I indeed see pr60576 (assumed_rank_7.f90), pr64921 (class_allocate_18.f90), and
pr64986 (class_to_type_4.f90). I also see 40+ failures associated with scan-*
which are probably expected: -fsanitize=address may change optimizations.
Finally (this PR) the tests gfortran.dg/io_real_boz(2|_[45]).f90 give outputs
of the kind

=================================================================
==24090==ERROR: AddressSanitizer: global-buffer-overflow on address
0x00010c37ce04 at pc 0x00010c3948c8 bp 0x7fff53882e40 sp 0x7fff538825f0
READ of size 3 at 0x00010c37ce04 thread T0
    #0 0x10c3948c7  (/opt/gcc/gcc4.10w/lib/libasan.2.dylib+0x138c7)
    #1 0x10d15f1c5  (/opt/gcc/gcc4.10w/lib/libgfortran.3.dylib+0xc01c5)
    #2 0x10c37cd9f 
(/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out+0x100000d9f)

0x00010c37ce04 is located 60 bytes to the left of global variable '*LC4'
defined in '/opt/gcc/_clean/gcc/testsuite/gfortran.dg/io_real_boz_5.f90'
(0x10c37ce40) of size 1
0x00010c37ce04 is located 0 bytes to the right of global variable '*LC3'
defined in '/opt/gcc/_clean/gcc/testsuite/gfortran.dg/io_real_boz_5.f90'
(0x10c37ce00) of size 4
...


             reply	other threads:[~2015-02-17 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 10:07 dominiq at lps dot ens.fr [this message]
2015-04-03  0:03 ` [Bug fortran/65089] " hp at gcc dot gnu.org
2015-04-03  8:27 ` dominiq at lps dot ens.fr
2015-04-03 20:11 ` jvdelisle at gcc dot gnu.org
2015-04-03 22:25 ` jvdelisle at gcc dot gnu.org
2015-04-03 22:29 ` dominiq at lps dot ens.fr
2015-04-04  8:53 ` dominiq at lps dot ens.fr
2015-04-08 13:42 ` jakub at gcc dot gnu.org
2015-04-09  0:00 ` jvdelisle at gcc dot gnu.org
2015-04-09  6:39 ` jakub at gcc dot gnu.org
2015-04-09  8:48 ` dominiq at lps dot ens.fr
2015-04-09 12:08 ` jvdelisle at gcc dot gnu.org
2015-04-12  4:19 ` jvdelisle at gcc dot gnu.org
2015-04-12  7:47 ` dominiq at lps dot ens.fr
2015-04-15  1:27 ` jvdelisle at gcc dot gnu.org
2015-04-15  1:58 ` jvdelisle at gcc dot gnu.org
2015-09-07  9:57 ` dominiq at lps dot ens.fr

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-65089-4@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).