public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63764] [5 Regression] ICE: in verify_ssa, at tree-ssa.c:939
Date: Tue, 18 Nov 2014 17:18:00 -0000	[thread overview]
Message-ID: <bug-63764-4-5HUVBAU30f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63764-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63764

--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 18 Nov 2014, jakub at gcc dot gnu.org wrote:

> > I'd think it's reasonable to subscript a non-lvalue vector (including e.g. 
> > the return value of a function with vector return type) - this might of 
> > course need to create a temporary object, as with non-lvalue arrays.
> 
> For rhs yes, supposedly.  But not for lhs.  So, perhaps if *vecp is not an
> lvalue, assign to temporary and take address of that, but then in the end wrap
> the result of the subscripting into NON_LVALUE_EXPR, so that we actually error
> out on the testcase?

Yes, that sort of thing - make the result of subscripting not an lvalue if 
the expression subscripted is not an lvalue, so that an error results on 
assigning to it.


  parent reply	other threads:[~2014-11-18 17:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 17:53 [Bug middle-end/63764] New: nternal compiler error: " mkg at us dot ibm.com
2014-11-07  9:29 ` [Bug tree-optimization/63764] [5 Regression] ICE: " trippels at gcc dot gnu.org
2014-11-18 10:23 ` [Bug target/63764] " jakub at gcc dot gnu.org
2014-11-18 15:34 ` joseph at codesourcery dot com
2014-11-18 16:36 ` jakub at gcc dot gnu.org
2014-11-18 16:55 ` joseph at codesourcery dot com
2014-11-18 17:02 ` jakub at gcc dot gnu.org
2014-11-18 17:18 ` joseph at codesourcery dot com [this message]
2014-11-19 14:36 ` jakub at gcc dot gnu.org
2014-11-19 16:25 ` joseph at codesourcery dot com
2014-11-20 12:48 ` rguenth at gcc dot gnu.org
2014-11-21  9:26 ` jakub at gcc dot gnu.org
2014-11-21  9:35 ` jakub 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-63764-4-5HUVBAU30f@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: link
Be 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).