------- Comment #22 from pinskia at gcc dot gnu dot org 2005-11-16 13:36 ------- (In reply to comment #21) > For the libgfortran issue (libgfortran uses __imag__ as a lvalue) what should > be done? Who can decide whether __imag__ is or isn't a lvalue? Sorry to ask > for > the obvious, but I'm lost. > Anyhow, if the change in behaviour between 4.0 and 4.1 is intended, it should > surely be noted somewhere.
Note I never said __imag__ a should not act like an lvalue. I just said that __imag__ a = b; acts like a = COMPLEX<REAL<a>, b> which is just like what a = (a&0xFFFF0000)|(b&0x0000FFFF) does. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23497
