[cfe-dev] New guy on the list trying to fix windows things

Jb Feldman jb.feldman at kyrus-tech.com
Sat Jan 11 08:24:15 PST 2014

That is a good suggestion, thank you. I should have done that yesterday,
but zygoloid was actually able to help me figure some things out. As a
result I have something that hopefully is even better, a bug report:

This can be achieved with either the minimal code in the bug report, or if
you are using Visual Studio, the way I originally discovered the bug was to
simply include the file "#include <atltime.h>" and try to compile with no
fancy options.

Zygoloid diagnosed for me that the "bug" actually stems from syntactically
incorrect code, but because it is prevalent in MS headers and cl.exe
supports it, I think (and he agreed) that it is something clang should
consider supporting.


On Sat, Jan 11, 2014 at 11:13 AM, Tobias Grosser <tobias at grosser.es> wrote:

> On 01/11/2014 12:04 AM, Jb Feldman wrote:
>> Thanks for your response. I understand that LLVM is working toward Windows
>> support, which is why they want me to get more actively involved in trying
>> to fix at least the problems that we have already. I'll definitely file
>> the
>> ticket at llvm.org, but I was hoping you might be able to tell me where
>> to
>> look in source to figure out how to start fixing things.
>> Currently I'm poking around in the Sema directory, hoping to find
>> something. That is at least where the error is being thrown, but it may
>> not
>> be where the bug is. The thing you mentioned about delayed template
>> parsing
>> sounds like it might be of particular interest. Can you point me to where
>> that magic happens?
> Hi JB,
> I unfortunately have no idea about all this. However, for other people to
> help you, it is normally extremely helpful if you can provide a reduced
> test case for which you can reproduce the problem with clang trunk (the
> latest version). In the optimal case you provide this test case (e.g.
> single C file) together with the command line options you have run clang
> trunk, the output you got and an explanation on how the output you got
> differs from what you expect.
> (I know it is probably possible to guess your problem from the links you
> provided, but such guessing often is rather inaccurate and not everybody
> will even try to do so).
> Cheers,
> Tobias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140111/a46dc9a3/attachment.html>

More information about the cfe-dev mailing list