public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36239]  New: ICE: gfc_validate_kind(): Got bad kind
Date: Thu, 15 May 2008 05:47:00 -0000	[thread overview]
Message-ID: <bug-36239-13404@http.gcc.gnu.org/bugzilla/> (raw)

James Van Buskirk found the following bug, see
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/1cc4ce4ecec2933d


         integer, parameter :: k_k11 = kind(int(Parg1,kind=k11))
                                                               1
Internal Error at (1):
gfc_validate_kind(): Got bad kind


 module bugmod
   parameter(ik1 = selected_int_kind(2))
   implicit complex (P)
   contains
      subroutine bug1(P1)
         integer(ik1), parameter :: k11 = ik1
         complex, parameter :: carg1 = 0
         parameter(Parg1 = carg1)
         integer, parameter :: k_k11 = kind(int(Parg1,kind=k11))
      end subroutine bug1
end module bugmod


-- 
           Summary: ICE: gfc_validate_kind(): Got bad kind
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


             reply	other threads:[~2008-05-15  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  5:47 burnus at gcc dot gnu dot org [this message]
2008-05-15 17:44 ` [Bug fortran/36239] " kargl at gcc dot gnu dot org
2008-05-15 18:26 ` kargl at gcc dot gnu dot org
2008-05-16  3:42 ` jvdelisle at gcc dot gnu dot org
2008-05-16  3:43 ` jvdelisle at gcc dot gnu dot org
2008-12-28  4:17 ` pinskia 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-36239-13404@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).