This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/23497] [4.1 regression] Bogus 'is used uninitialized...' warning about std::complex<T>
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Nov 2005 13:36:32 -0000
- Subject: [Bug middle-end/23497] [4.1 regression] Bogus 'is used uninitialized...' warning about std::complex<T>
- References: <bug-23497-2589@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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