http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #5 from Joseph S. Myers ---
Author: jsm28
Date: Tue Dec 3 02:47:13 2013
New Revision: 205615
URL: http://gcc.gnu.org/viewcvs?rev=205615&root=gcc&view=rev
Log:
PR c/58235
c:
* c-typeck.c (build_modify_expr): Diagnose assignmen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #4 from farouk jouti ---
the link contains all the necessary information about the bug (just check the
comments and answers) ;)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
farouk jouti changed:
What|Removed |Added
CC||farouk.jouti at live dot co.uk
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #2 from Olivier Gay ---
Still, constraint of assignment (c90, 6.3.16) requires the left operand of
assignment to be a modifiable lvalue. But c object array is not a modifiable
lvalue as arrays are not modifiable lvalues (6.2.2.1).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58235
--- Comment #1 from Andrew Pinski ---
This seems correct: See also bug 461. non-lvalue arrays do not decay to
pointers in C90/C89.
