public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paul dot richard dot thomas at cea dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27889] [4.1/4.2 Regression] ICE on complex assignment in nested function Date: Tue, 06 Jun 2006 07:14:00 -0000 [thread overview] Message-ID: <20060606064757.22009.qmail@sourceware.org> (raw) In-Reply-To: <bug-27889-10979@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from paul dot richard dot thomas at cea dot fr 2006-06-06 06:47 ------- Noting the non-fortran tilt on this, it is interesting that implicit COMPLEX (a-z) CALL foo CONTAINS SUBROUTINE foo t = s + s END SUBROUTINE foo END is OK and produces declarations for s and t in foo. Alternatively, declaring s and t in foo also works. However, COMPLEX s, t CALL foo CONTAINS SUBROUTINE foo t = s + s END SUBROUTINE foo END puts the declarations in MAIN__, thusly: foo () { t = s + s; MAIN__ () { complex4 s; complex4 t; static void foo (void); _gfortran_set_std (70, 127, 0); foo (); } and triggers the ICE for any optimization level. In fortran parlance, it is host or use association of the complex type that is broken. Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27889
next prev parent reply other threads:[~2006-06-06 6:48 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-04 8:28 [Bug fortran/27889] New: gfortran 4.1.1 ICE on espresso (PWscf) spyderous at gentoo dot org 2006-06-04 11:24 ` [Bug middle-end/27889] ICE on complex assignment fxcoudert at gcc dot gnu dot org 2006-06-04 11:50 ` [Bug fortran/27889] " fxcoudert at gcc dot gnu dot org 2006-06-04 14:38 ` fxcoudert at gcc dot gnu dot org 2006-06-04 15:16 ` pinskia at gcc dot gnu dot org 2006-06-04 21:05 ` pinskia at gcc dot gnu dot org 2006-06-04 21:09 ` [Bug middle-end/27889] " pinskia at gcc dot gnu dot org 2006-06-04 22:33 ` [Bug middle-end/27889] [4.1/4.2 Regression] ICE on complex assignment in nested function pinskia at gcc dot gnu dot org 2006-06-06 6:15 ` paul dot richard dot thomas at cea dot fr 2006-06-06 6:18 ` pinskia at gcc dot gnu dot org 2006-06-06 6:42 ` paul dot richard dot thomas at cea dot fr 2006-06-06 7:14 ` paul dot richard dot thomas at cea dot fr [this message] 2006-06-09 7:39 ` pinskia at gcc dot gnu dot org 2006-06-09 8:56 ` paul dot richard dot thomas at cea dot fr 2006-06-24 19:00 ` pinskia at gcc dot gnu dot org 2006-06-26 0:55 ` roger at eyesopen dot com 2006-07-05 17:56 ` mmitchel at gcc dot gnu dot org 2006-07-05 17:59 ` pinskia at gcc dot gnu dot org 2006-07-07 17:03 ` mmitchel at gcc dot gnu dot org 2006-07-13 18:19 ` janis at gcc dot gnu dot org 2006-07-17 17:11 ` rth at gcc dot gnu dot org 2006-07-18 1:18 ` rth at gcc dot gnu dot org 2006-07-20 15:44 ` [Bug middle-end/27889] [4.1 " rth at gcc dot gnu dot org 2006-07-20 22:33 ` 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=20060606064757.22009.qmail@sourceware.org \ --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: linkBe 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).