gcc/clang interoperability problem with a custom "samba" build in recent -current.

[Julian Elischer]

On 25/7/18 12:40 am, Julian Elischer wrote:
> On 22/7/18 4:32 am, Dimitry Andric wrote:
>> On 21 Jul 2018, at 21:11, Yuri Pankov <yuripv at yuripv.net> wrote:
>>> Yuri Pankov wrote:
>>>> Julian Elischer wrote:
>> ...
>>>>>> anyone know if there is a clang equivalent of -Wp, -E,-lang-asm?
>>>> In later GCC versions the cpp's -lang-asm seems to be deprecated in
>>>> favor of -x assembler-with-cpp as it conflicts with -l option.
>>>> Could you try changing the -Wp,-E,-lang-asm to 
>>>> -Wp,-E,-xassembler-with-cpp?
I did this but if failed.. I had to reread this email  a few times to 
think of replacing the whole
-Wp,-E,-lang-asm  with just  -xassembler-with-cpp!


>>> Just tried it myself, and if you indeed mean the 
>>> third_party/aesni-intel/aesni-intel_asm.c, the following seems to 
>>> work for me:
>>>
>>> clang -xassembler-with-cpp -c 
>>> third_party/aesni-intel/aesni-intel_asm.c
>> Yes, that is exactly what I suggested to Julian on IRC.  The point is
>> that the ".c" extension is misleading, it should more likely be a ".S"
>> extension.  But maybe this source file is used for multiple purposes.
>>
>> Note that -x assembler-with-cpp should also work fine for gcc.
Ah..  the trick is to remove the -Wp,-E as well...
>>
>> -Dimitry
>>
> thanks
>
> I tried that but the version of the file we have has several lines 
> that caused problems...
>
> a lot of the assembler has assembler comments (starting with '#') 
> which clang complained about and died..
>
> it also had #.align 4
>
> which I HOPE is just a commented out line..
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"
>