[cfe-dev] Clang accepts x86 specific options when cross compiling for arm

[Craig Topper via cfe-dev]

Though not having an input file is probably a fatal error that suppresses
any other warnings/errors from printing.

~Craig

On Wed, Jul 26, 2017 at 6:13 PM, Craig Topper <craig.topper at gmail.com>
wrote:

> You should have gotten an "argument unused during compilation" warning
> that you can promote to an error.
>
> ~Craig
>
> On Wed, Jul 26, 2017 at 5:41 PM, Khem Raj via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
>> Hi
>>
>> I am compiling a package which pokes at compiler for -msse4.2 option and
>> if compiler accepts it then it happily adds the intel specific
>> intrinsics to code path. This works fine in cross compile environment
>> with gcc since gcc when configure for cross compiling for arm targets
>> rejects this option however with clang, configured for multiple targets
>>
>> LLVM_TARGETS_TO_BUILD = "AArch64;ARM;Mips;PowerPC;X86"
>>
>> it happily accepts -msse4.2 when called to cross compile for arm.
>>
>> arm-bec-linux-gnueabi-clang -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard
>> -mcpu=cortex-a7 -mlittle-endian -march=armv7a
>> --sysroot=/mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-b
>> ec-linux-gnueabi/leveldb/1.20+gitAUTOINC+a53934a3ae-r0/recipe-sysroot
>>  -O2 -msse4.2
>> clang-5.0: error: no input files
>>
>> I believe it would be better if clang could cross check for target
>> options and error out and flag these kind of incompatible combinations
>>
>> may be there is already an option to do so, I would be happy to know
>> since this would fix my issue once for all.
>>
>> Thanks
>> -Khem
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20170726/fe60a612/attachment.html>