------- Comment #21 from fxcoudert at gcc dot gnu dot org 2005-11-16 13:19 ------- (In reply to comment #19) > There are only two choices: either __imag__ is an lvalue, and the code in > Comment #1 is valid, or __imag__ is not an lvalue, and the compiler should > issue an error.
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. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23497
