diff options
| author | Rafael Espindola <rafael.espindola@gmail.com> | 2012-10-09 20:46:28 +0000 |
|---|---|---|
| committer | Rafael Espindola <rafael.espindola@gmail.com> | 2012-10-09 20:46:28 +0000 |
| commit | fc3fc0c9362ac3efd347f2c48d61bba479503f2d (patch) | |
| tree | c5fa10176ac42886fe90b729ad12067aae03b5b1 /clang/test/Driver/gcc_forward.c | |
| parent | 2f7bf410916df36428076f135defb0262423b273 (diff) | |
| download | bcm5719-llvm-fc3fc0c9362ac3efd347f2c48d61bba479503f2d.tar.gz bcm5719-llvm-fc3fc0c9362ac3efd347f2c48d61bba479503f2d.zip | |
The clang driver has a fairly fancy support for executing gcc instead of
clang itself. This dates back to clang's early days and while it looks like
some of it is still used (for kext for example), other parts are probably dead.
Remove the -ccc-clang-archs option and associated code. I don't think there
is any remaining setup where clang doesn't support an architecture but it can
expect an working gcc cross compiler to be available.
A nice side effect is that tests no longer need to differentiate architectures
that are included in production builds of clang and those that are not.
llvm-svn: 165545
Diffstat (limited to 'clang/test/Driver/gcc_forward.c')
| -rw-r--r-- | clang/test/Driver/gcc_forward.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/test/Driver/gcc_forward.c b/clang/test/Driver/gcc_forward.c index 77f401b92e5..8eead214fee 100644 --- a/clang/test/Driver/gcc_forward.c +++ b/clang/test/Driver/gcc_forward.c @@ -1,7 +1,7 @@ // Check that we don't try to forward -Xclang or -mlinker-version to GCC. // // RUN: %clang -target powerpc-unknown-unknown \ -// RUN: -ccc-clang-archs i386 -c %s \ +// RUN: -c %s \ // RUN: -Xclang foo-bar \ // RUN: -mlinker-version=10 -### 2> %t // RUN: FileCheck < %t %s |
