[cfe-dev] [PATCH] MS compatibility flag implies delayed parsing

Matthieu Monrocq matthieu.monrocq at gmail.com
Tue Nov 8 10:09:44 PST 2011


Le 8 novembre 2011 15:56, Aaron Ballman <aaron at aaronballman.com> a écrit :

> On Mon, Nov 7, 2011 at 4:55 PM, Eli Friedman <eli.friedman at gmail.com>
> wrote:
> > I don't see why the changes to lib/Frontend/CompilerInvocation.cpp and
> > include/clang/Driver/CC1Options.td are necessary.  The changes to
> > lib/Driver/Tools.cpp look fine.
>
> I'm not certain I understand why the two are separate from one
> another.  Can you give me a quite education on the topic?
>
> On Mon, Nov 7, 2011 at 5:02 PM, Francois Pichet <pichet2000 at gmail.com>
> wrote:
> > How about we remove --fdelayed-template-parsing altogether and check
> > for fms-compatibility to do late template parsing?
> >
> > Anybody else needs delayed template parsing without microsoft
> compatibility?
>
> That would be the best solution IMO, but I wasn't sure if anyone was
> relying on them being separated.  If no one objects, I can remove the
> delayed template parsing param and simply roll the functionality into
> MS compatibility.  But I do have one question on this -- should I
> simply remove the flag entirely (so people start getting warnings
> about unused flags), or should I leave the flag in and make it no-op?
>
> Thanks!
>
> ~Aaron
>
>
As far as I remember it was Doug indicating that it could be beneficial to
have it separately, as I think Francois had demonstrated that only parsing
on-demand (at the end of the TU) improved performance somewhat.

-- Matthieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20111108/2df23245/attachment.html>


More information about the cfe-dev mailing list