public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "deji_aking at yahoo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37974]  New: gfortran runtime segmentation fault
Date: Fri, 31 Oct 2008 02:07:00 -0000	[thread overview]
Message-ID: <bug-37974-8911@http.gcc.gnu.org/bugzilla/> (raw)

Using Gfortran, I'm getting a segmentation fault from running a code which
reduces to the following;
...
   PROGRAM seg_main
   INTEGER :: ip
   real :: sig

        ip = 26314400
        call seg_sub(ip, sig, 1)
        write(*,*) 'sig is', sig
   END PROGRAM

   SUBROUTINE seg_sub(ip, p, kind0)

      implicit none
      integer ip, kind0
      real p

      kind0 = 2 - 1
      p = ip

      return
   END SUBROUTINE
...
I'm not sure if the code violates some fortran standards, although it seems
valid to me. But I think gfortran should give some warning or error messages
instead of just segfaulting. The code works fine with pgf90 on Linux and xlf on
AIX, but similarly segfault with ifort on Linux.


-- 
           Summary: gfortran runtime segmentation fault
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: deji_aking at yahoo dot ca


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


             reply	other threads:[~2008-10-31  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31  2:07 deji_aking at yahoo dot ca [this message]
2008-10-31  2:21 ` [Bug fortran/37974] " kargl at gcc dot gnu dot org
2008-10-31  3:33 ` deji_aking at yahoo dot ca
2008-10-31  3:41 ` kargl 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-37974-8911@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).