diff options
author | Bill Schmidt <wschmidt@linux.vnet.ibm.com> | 2013-07-03 15:36:02 +0000 |
---|---|---|
committer | Bill Schmidt <wschmidt@linux.vnet.ibm.com> | 2013-07-03 15:36:02 +0000 |
commit | b3b804e442d85dd39340af3edb608d687b591e74 (patch) | |
tree | 04aa70cb3851f0803858924f8c035cb846ca2576 /llvm/test/Object/nm-error.test | |
parent | f432f857771bc91313f0c682017d5f8e7f28d499 (diff) | |
download | bcm5719-llvm-b3b804e442d85dd39340af3edb608d687b591e74.tar.gz bcm5719-llvm-b3b804e442d85dd39340af3edb608d687b591e74.zip |
Fix PR16454: Don't #include altivec.h when preprocessing assembly.
When the -maltivec flag is present, altivec.h is auto-included for the
compilation. This is not appropriate when the job action is to
preprocess a file containing assembly code. So don't do that.
I was unable to convert the test in the bug report into a regression
test. The original symptom was exposed with:
% touch x.S
% ./bin/clang -target powerpc64-unknown-linux-gnu -maltivec -S -o - x.S
I tried this test (and numerous variants) on a PPC64 system:
----------------------------------------------------------------------------
// RUN: touch %t
// RUN: %clang -maltivec -S %t -o - | FileCheck %s
// Verify that assembling an empty file does not auto-include altivec.h.
// CHECK-NOT: static vector
----------------------------------------------------------------------------
However, this test passes for some reason even on a clang built
without the fix. I'd be happy to add a test case but at this point
I'm not able to figure one out, and I don't want to hold up the patch
unnecessarily. Please let me know if you have ideas.
Thanks,
Bill
llvm-svn: 185544
Diffstat (limited to 'llvm/test/Object/nm-error.test')
0 files changed, 0 insertions, 0 deletions