[cfe-dev] Specific clang-cl preprocessor emulation problem

James Dennett via cfe-dev cfe-dev at lists.llvm.org
Fri Apr 15 16:17:05 PDT 2016


On Fri, Apr 15, 2016 at 4:10 PM, Edward Diener via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> On 4/15/2016 6:45 PM, Jonathan Roelofs via cfe-dev wrote:
>
>>
>>
>> On 4/15/16 4:32 PM, Edward Diener via cfe-dev wrote:
>>
>>>
>>> 3) I do not know what your reference to macro_paste_identifier_error.c
>>> means.
>>>
>>
>> clang/test/Preprocessor/macro_paste_identifier_error.c
>>
>> I assume that is a source file used to build clang-cl.
>>>
>>
>> No, it's a test.
>>
>
> I see it but I don't understand why you should be expecting a programmer
> using clang-cl ( or clang/clang++ targeting VC++ ) to have to pass a
> compiler option to emulate VC++ when you have already pushed clang-cl as
> emulating VC++ by default.
>
>
Please, don't assume that anyone is expecting such a thing.   I was just
providing the test as an example of how things work today.

My reason for asking whether you'd tried it was to ascertain whether
disabling that warning would resolve your issue.  It sounds like it would,
so thank you for confirming that.

MSVC++ support is still fairly new, and Boost PP pushes the limits.  I
suspect that people are entirely open to changing this, given a polite
request and a straightforward rationale.  I think (though I'm not sure)
that MSVC++ mode turns off various other diagnostics already.

-- James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160415/e7ac1e74/attachment.html>


More information about the cfe-dev mailing list