[cfe-dev] Parsing, pretty-printing, and compiling the result should work, right?

Chris Lattner clattner at apple.com
Mon Jan 19 13:32:54 PST 2009


On Jan 19, 2009, at 12:07 AM, Roberto Bagnara wrote:
>> For example, mine is
>> "make clang a production quality C compiler sooner rather than  
>> later".
>
> Good.  But since you cannot compile what you cannot parse, our agendas
> have a significant overlap: actually, mine is a strict subset of  
> yours.
> This was actually my argument when I convinced my group to use clang
> ("they certainly will want to correctly parse all the code out  
> there").

Yep we do.  However, while I'd love to see designated initializers  
happen sooner rather than later (and I'm thrilled that they may be  
happening soon!) I'd personally prioritize basic x86-64 codegen above  
designators.

>> 4) find a way to work around the problem.
>
> We will do that for all the remaining problems.  This is actually a
> tough decision for me: if 2749 and 3261 are not fixed in a reasonable
> time frame we will have to drop clang and I will have wasted the
> time of several people.

Hopefully they will get fixed then!

-Chris



More information about the cfe-dev mailing list