public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neil.n.carlson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45794] New: internal compiler error: Segmentation fault
Date: Sat, 25 Sep 2010 22:10:00 -0000	[thread overview]
Message-ID: <bug-45794-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: internal compiler error: Segmentation fault
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: neil.n.carlson@gmail.com


The following code causes an internal compiler error with the
current trunk:

$ gfortran --version
GNU Fortran (GCC) 4.6.0 20100924 (experimental)

subroutine foo (vector, mask)
  real :: vector(:)
  logical, optional :: mask(:)
  integer :: loc(1)
  if (present(mask)) then
    loc = maxloc(vector, mask)
  end if
end subroutine

$ gfortran -c bug3.f90 
bug3.f90: In function ‘foo’:
bug3.f90:6:0: internal compiler error: Segmentation fault

Note that this bug does not exist in 4.4 (or 4.5 I think).


             reply	other threads:[~2010-09-25 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 22:10 neil.n.carlson at gmail dot com [this message]
2010-09-25 22:14 ` [Bug fortran/45794] [4.6 Regression] ICE: Segmentation fault in gfc_conv_procedure_call burnus at gcc dot gnu.org
2010-09-30 11:18 ` rguenth at gcc dot gnu.org
2010-10-02 11:57 ` janus at gcc dot gnu.org
2010-11-12 20:27 ` jvdelisle at gcc dot gnu.org
2010-11-12 23:19 ` jvdelisle at gcc dot gnu.org
2010-11-12 23:25 ` jvdelisle at gcc dot gnu.org
2010-11-12 23:29 ` jvdelisle 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-45794-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).