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/55501] [F03] ICE using MERGE in constant expr Date: Wed, 28 Nov 2012 14:54:00 -0000 [thread overview] Message-ID: <bug-55501-4-8vJ2hepeB2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55501-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55501 --- Comment #12 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-11-28 14:54:33 UTC --- (In reply to comment #10) > integer :: i(-1:1) = 0 > print *, lbound(merge(i,i,.true.)) > Without the patch, this prints: > 1 > And with the patch: > -1 Makes perfectly sense: For "lbound(array,dim)": "If ARRAY is a whole array and either ARRAY is an assumed-size array of rank DIM or dimension DIM of ARRAY has nonzero extent, LBOUND (ARRAY, DIM) has a value equal to the lower bound for subscript DIM of ARRAY. Otherwise the result value is 1." With "whole array array component or array name without further quali\fcation (6.5.2)" Thus "lbound(i)" is a whole-array, "lbound(i(:))" or "lbound(merge(i,i,.true))" is not. I think the simplest it to replace "lbound (merge(i,i,.true.)" by "lbound( (i) )" [e->expr_type = EXPR_OP && e->value.op.op == INTRINSIC_PARENTHESES]. Possibly only if expr_type == EXPR_VARIABLE as otherwise the INTRINSIC_PARENTHESES will hamper further optimization (unless -fno-protect-parens).
next prev parent reply other threads:[~2012-11-28 14:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-28 0:27 [Bug fortran/55501] New: " longb at cray dot com 2012-11-28 0:37 ` [Bug fortran/55501] " longb at cray dot com 2012-11-28 9:16 ` [Bug fortran/55501] [F03] " janus at gcc dot gnu.org 2012-11-28 9:40 ` janus at gcc dot gnu.org 2012-11-28 10:11 ` janus at gcc dot gnu.org 2012-11-28 10:36 ` janus at gcc dot gnu.org 2012-11-28 10:49 ` burnus at gcc dot gnu.org 2012-11-28 10:50 ` janus at gcc dot gnu.org 2012-11-28 10:55 ` burnus at gcc dot gnu.org 2012-11-28 11:04 ` burnus at gcc dot gnu.org 2012-11-28 12:17 ` janus at gcc dot gnu.org 2012-11-28 12:22 ` janus at gcc dot gnu.org 2012-11-28 14:54 ` burnus at gcc dot gnu.org [this message] 2013-09-26 4:43 ` longb at cray dot com
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-55501-4-8vJ2hepeB2@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).