public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15326] [4.0 only] ICE with assumed length character strings Date: Sun, 18 Sep 2005 19:53:00 -0000 [thread overview] Message-ID: <20050918195257.25061.qmail@sourceware.org> (raw) In-Reply-To: <20040506164815.15326.Tobias.Schlueter@physik.uni-muenchen.de> ------- Additional Comments From tkoenig at gcc dot gnu dot org 2005-09-18 19:52 ------- Not fixed in 4.0: $ cat > reduced.f90 program Decapitation implicit none integer, parameter :: STRING_LENGTH = 80 character (len = STRING_LENGTH) :: Text_1, Text_2 Text_2 = Decap (Text_1) stop contains function Decap (String) result (New_String) character (len = *), intent(in) :: String character (len = Len(String)) :: New_String return end function Decap end program Decapitation $ gfortran reduced.f90 reduced.f90: In function 'MAIN__': reduced.f90:11: internal compiler error: in gfc_conv_function_call, at fortran/trans-expr.c:1108 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. $ gfortran -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0/configure --prefix=/home/ig25 --enable-languages=c,fortran Thread model: posix gcc version 4.0.2 20050917 (prerelease) -- What |Removed |Added ---------------------------------------------------------------------------- CC| |tkoenig at gcc dot gnu dot | |org Status|RESOLVED |REOPENED Known to fail| |4.0.2 Known to work| |4.1.0 Resolution|FIXED | Summary|ICE with assumed length |[4.0 only] ICE with assumed |character strings |length character strings Target Milestone|--- |4.0.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15326
next prev parent reply other threads:[~2005-09-18 19:53 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-06 16:48 [Bug fortran/15326] New: [gfortran] " Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-06 17:08 ` [Bug fortran/15326] " Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-06 18:02 ` pinskia at gcc dot gnu dot org 2004-05-27 3:08 ` pinskia at gcc dot gnu dot org 2004-06-13 9:25 ` pinskia at gcc dot gnu dot org 2004-06-27 20:30 ` [Bug fortran/15326] " pinskia at gcc dot gnu dot org 2004-08-09 15:56 ` pinskia at gcc dot gnu dot org 2004-09-25 15:04 ` tobi at gcc dot gnu dot org 2004-10-10 21:04 ` tobi at gcc dot gnu dot org 2004-10-10 21:08 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2005-01-06 14:40 ` tobi at gcc dot gnu dot org 2005-02-12 21:55 ` pinskia at gcc dot gnu dot org 2005-08-31 15:26 ` pinskia at gcc dot gnu dot org 2005-08-31 20:54 ` rsandifo at gcc dot gnu dot org 2005-09-08 18:46 ` cvs-commit at gcc dot gnu dot org 2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org 2005-09-18 19:53 ` tkoenig at gcc dot gnu dot org [this message] 2005-09-18 20:09 ` [Bug fortran/15326] [4.0 only] " rsandifo at gcc dot gnu dot org 2005-09-18 20:27 ` pinskia at gcc dot gnu dot org [not found] <bug-15326-7283@http.gcc.gnu.org/bugzilla/> 2005-11-24 6:06 ` 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=20050918195257.25061.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).