public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52093] [4.6/4.7 Regression] Extra parenthesis with Size and Shape functions argument cause internal compiler error: Segmentation fault Date: Thu, 02 Feb 2012 08:29:00 -0000 [thread overview] Message-ID: <bug-52093-4-zaWFOydMRS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52093-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52093 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org Target Milestone|--- |4.6.3 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-02 08:28:27 UTC --- For me (on 4.7), SHAPE and LBOUND work, only SIZE and UBOUND cause an ICE. The segfault happens for SIZE and UBOUND at: Invalid read of size 4 at 0x5383E0: gfc_simplify_size (simplify.c:5553) (When patching, remember that UBOUND((X)) and UBOUND(X) are different, it the lower bound of X is not 1.) Untested patch: --- a/gcc/fortran/simplify.c +++ b/gcc/fortran/simplify.c @@ -5543,2 +5543,3 @@ gfc_simplify_size (gfc_expr *array, gfc_expr *dim, gfc_expr *kind) case INTRINSIC_UMINUS: + case INTRINSIC_PARENTHESES: replacement = array->value.op.op1;
next prev parent reply other threads:[~2012-02-02 8:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-02 7:37 [Bug fortran/52093] New: " m.rahmani at aut dot ac.ir 2012-02-02 8:17 ` [Bug fortran/52093] [4.6/4.7 Regression] " dominiq at lps dot ens.fr 2012-02-02 8:29 ` burnus at gcc dot gnu.org [this message] 2012-02-02 9:18 ` jakub at gcc dot gnu.org 2012-02-02 21:02 ` burnus at gcc dot gnu.org 2012-02-03 20:38 ` burnus at gcc dot gnu.org 2012-02-03 21:54 ` 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-52093-4-zaWFOydMRS@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).