http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
--- Comment #7 from vries at gcc dot gnu.org ---
Author: vries
Date: Wed Nov 27 10:00:48 2013
New Revision: 205439
URL: http://gcc.gnu.org/viewcvs?rev=205439root=gccview=rev
Log:
Handle vector increment/decrement in build_unary_op
2013-11-27
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
vries at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
vries at gcc dot gnu.org changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
--- Comment #3 from Marc Glisse glisse at gcc dot gnu.org ---
I wonder if it would take more than replacing:
inc = integer_one_node;
with something like:
inc = VECTOR_TYPE_P (argtype)
? build_one_cst
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
--- Comment #4 from vries at gcc dot gnu.org ---
We already support v=v+1, so it wouldn't be a large extension.
Hmm, indeed. If found some code in cp_builld_binary_op marked with this
comment:
...
/* In case when one of the operands of the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
--- Comment #5 from Marc Glisse glisse at gcc dot gnu.org ---
(In reply to vries from comment #4)
I've tried to do something similar in cp_build_unary_op. Tentative patch:
That seems very complicated. We know the arguments, so we know which has
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
vries at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.8.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59032
Volker Reichelt reichelt at gcc dot gnu.org changed:
What|Removed |Added
Keywords||diagnostic,
10 matches
Mail list logo
