public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcesari69 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58157] New: ICE on character function with len given by a PURE function Date: Wed, 14 Aug 2013 15:19:00 -0000 [thread overview] Message-ID: <bug-58157-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58157 Bug ID: 58157 Summary: ICE on character function with len given by a PURE function Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: dcesari69 at gmail dot com Created attachment 30655 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30655&action=edit Fortran source for reproducing ICE Hello, the attached simplified code contains a module with a CHARACTER function whose results' length is given by another PURE function, which I assume is correct Fortran 95 and I have used succesfully in other contexts. The module compiles well, but as soon as the function is encountered in another piece of code using the module, I get an ICE (+segfault): ==== [davide@localhost ~]$ rm -f *.mod; LANG= gfortran -c icetest.f90 icetest.f90: In function 'icetest': icetest.f90:34:0: internal compiler error: Segmentation fault tkey = strtofchar_chararr(key) ! ICE here!!! ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. ==== It reminds somehow bug 55287: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55827, but that one is fixed in 4.9, while this remains. Same bug with older versions of gfortran. This is my first bug submission to gcc, so please forgive any procedural mistake. Thank you for your work, Davide
next reply other threads:[~2013-08-14 15:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-14 15:19 dcesari69 at gmail dot com [this message] 2013-08-14 16:15 ` [Bug fortran/58157] " janus at gcc dot gnu.org 2013-08-14 16:56 ` dominiq at lps dot ens.fr
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-58157-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: 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).