public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52059] New: [4.7 Regression] ICE in gfc_conv_variable
Date: Mon, 30 Jan 2012 21:24:00 -0000 [thread overview]
Message-ID: <bug-52059-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52059
Bug #: 52059
Summary: [4.7 Regression] ICE in gfc_conv_variable
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jakub@gcc.gnu.org
CC: mikael@gcc.gnu.org
subroutine baz
real(kind=8) :: a(99), b
interface bar
function bar (x, y)
integer, intent(in) :: x, y
real(kind=8), dimension((y-x)) :: bar
end function bar
end interface
b = 1.0_8
a = foo (bar(0,35) / dble(34), b)
contains
elemental real(kind=8) function foo(x, y)
real(kind=8), intent(in) :: x, y
foo = 1
end function foo
end subroutine baz
ICEs starting with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180906
(and, when b in the call is replaced with say 1.0_8, ICEs in gfc_conv_constant
and when the y argument from y is removed and the caller is adjusted too, ICEs
in gfc_trans_assignment.
next reply other threads:[~2012-01-30 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 21:24 jakub at gcc dot gnu.org [this message]
2012-01-30 21:31 ` [Bug fortran/52059] " jakub at gcc dot gnu.org
2012-01-30 23:29 ` burnus at gcc dot gnu.org
2012-01-31 1:08 ` jakub at gcc dot gnu.org
2012-01-31 5:57 ` pinskia at gcc dot gnu.org
2012-01-31 12:31 ` burnus at gcc dot gnu.org
2012-02-01 8:35 ` burnus at gcc dot gnu.org
2012-02-01 19:02 ` burnus at gcc dot gnu.org
2012-02-01 19:13 ` burnus 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-52059-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).