generalized lvalues

Mike Stump mrs@apple.com
Fri Nov 19 01:39:00 GMT 2004


On Nov 18, 2004, at 10:27 AM, Joe Buck wrote:
> Really?

AFAIK.

> Can you show some of the example errors?

Sounds boring and tedious, I don't see any benefit to doing that work.  
I've accepted the extension is gone and just plan on informing users it 
is gone.

If details about that would help bring it back and someone around here 
really wants to bring it back, then, they can furnish those details...  
:-)

> And are they really due to this extension specifically?

AFAIK.

The side world build people do the builds with newer compilers on the 
world, and then attempt to categorize the failures and the causes of 
those failures.  We get ICEs out of it, tightened up compilers, codegen 
bugs (link failures, assembly failures) and so on.  Usually the first 
in the series of bugs is routed through one of the compiler people to 
discern what category the propblem is in, and then farmed out as 
appropriate.  If two independent things cause otherwise identical error 
messages, then, it is possible there could be multiple causes.  In any 
event, what we do know, is that these things used to compile, and now 
don't.

Also, this is a lower bound number, as there can be other reasons why 
the project didn't get far enough in the compilation to find such a 
problem.



More information about the Gcc mailing list