public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35937]  New: char_result_5.f90 / char_result_6.f90 fail with -fdefault-integer-8
Date: Mon, 14 Apr 2008 19:18:00 -0000	[thread overview]
Message-ID: <bug-35937-10391@http.gcc.gnu.org/bugzilla/> (raw)

$ gfortran -g -fdefault-integer-8 char_result_5.f90 
$ gdb ./a.out
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(gdb) r
Starting program: /tmp/a.out 

Program received signal SIGSEGV, Segmentation fault.
0xb7f82664 in *_gfortran_string_scan (slen=9, str=0x804b480 "123456789",
setlen=1, set=0x0, back=-1080910905)
    at ../../../../gcc/trunk/libgfortran/intrinsics/string_intrinsics.c:300
300                   if (str[i] == set[j])


-- 
           Summary: char_result_5.f90 / char_result_6.f90 fail with -
                    fdefault-integer-8
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tkoenig at gcc dot gnu dot org
 BugsThisDependsOn: 32770


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35937


             reply	other threads:[~2008-04-14 19:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 19:18 tkoenig at gcc dot gnu dot org [this message]
2008-04-14 19:39 ` [Bug fortran/35937] " dominiq at lps dot ens dot fr
2008-04-14 19:46 ` tkoenig at gcc dot gnu dot org
2008-04-14 20:27 ` dominiq at lps dot ens dot fr
2008-05-12 17:44 ` [Bug fortran/35937] Wrong type for charlength of function fxcoudert at gcc dot gnu dot org
2008-05-12 17:45 ` fxcoudert at gcc dot gnu dot org
2008-05-12 18:27 ` fxcoudert at gcc dot gnu dot org
2008-05-12 18:27 ` fxcoudert at gcc dot gnu dot org
2008-07-23 16:29 ` pault at gcc dot gnu dot org
2008-08-08 21:39 ` jv244 at cam dot ac dot uk
2008-08-08 21:51 ` dominiq at lps dot ens dot fr
2008-08-23  8:15 ` fxcoudert at gcc dot gnu dot org
2008-11-28 14:33 ` pault at gcc dot gnu dot org
2008-11-28 14:33 ` pault at gcc dot gnu dot org
2008-11-30 13:15 ` pault at gcc dot gnu dot org
2008-12-02 20:05 ` dominiq at lps dot ens dot fr
2008-12-03  5:53 ` pault at gcc dot gnu dot org
2008-12-10 15:18 ` dominiq at lps dot ens dot fr
2008-12-10 16:19 ` dominiq at lps dot ens dot fr
2008-12-10 19:17 ` dominiq at lps dot ens dot fr
2008-12-11  9:39 ` pault at gcc dot gnu dot org
2008-12-11 10:02 ` dominiq at lps dot ens dot fr
2008-12-11 10:40 ` fxcoudert at gcc dot gnu dot org
2008-12-14 16:03 ` pault at gcc dot gnu dot org
2008-12-14 16:10 ` pault at gcc dot gnu dot org
2008-12-14 16:13 ` pault 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-35937-10391@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).