This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bug#300945: romeo: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Andreas Jochens <aj at andaco dot de>, Shaun Jackman <sjackman at gmail dot com>, 300945 at bugs dot debian dot org, gcc at sources dot redhat dot com
Date: Sat, 2 Apr 2005 17:02:16 -0500
Subject: Re: Bug#300945: romeo: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
References: <E1DDpzz-000366-8k@localhost.localdomain> <7f45d93905040213534279e4b5@mail.gmail.com> <4ffd289d78ce2f25ae4dfaa750e361b4@physics.uc.edu>

On Apr 2, 2005, at 4:57 PM, Andrew Pinski wrote:

On Apr 2, 2005, at 4:53 PM, Shaun Jackman wrote:
Can the GCC "C Extension" of "Generalized Lvalues" be enabled with a
switch in gcc-4.0?
No.

Note a better fix for the bug would be:

#define memUHeapSize(p,ver) \ *(ver>2 ? &((MemHeapHeaderPtr)p)->size : (ver>1 ? &((Mem2HeapHeaderPtr)p)->size : (&(Mem1HeapHeaderPtr)p)->size))

And then you get a lvalue.

-- Pinski

References:
- Re: Bug#300945: romeo: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
  - From: Shaun Jackman
- Re: Bug#300945: romeo: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]