4 Commits

Author	SHA1	Message	Date
Rafael Espindola	edaa444bda	Don't use the gcc driver for assembling. ... Clang knows how to use the gnu assembler directly from doing so on linux and hurd. The existing support worked out of the box on cygwin and mingw and I was able to bootstrap clang with it in both systems (with pending patches for the new mingw abi, but that is independent of the assembler). llvm-svn: 195554	2013-11-23 16:40:57 +00:00
Chandler Carruth	274b6f0c87	Update two options to my proposed syntax for user-facing driver options: ... -gcc-toolchain foo -> --gcc-toolchain=foo -target foo -> --target=foo I've added legacy aliases for the original spellings. I've updated the canonical tests to check both spellings, and switched all of the -gcc-toolchain usages elsewhere in the test suite to use the new one. I've updated some of the usages of -target to the new syntax, but will finish that in a separate entirely mechanical change once I'm sure this won't get rolled back for some reason (It touches a *huge* number of RUN lines in the test suite unsurprisingly). A nice result is that the three most common flags I end up using when doing cross compiles are all now consistent: --target=, --sysroot=, and --gcc-toolchain=. llvm-svn: 184408	2013-06-20 09:42:40 +00:00
NAKAMURA Takumi	2235e6da8f	test/Driver/target.c: Relax expression for "gcc.exe" on win32. ... llvm-svn: 149510	2012-02-01 15:16:22 +00:00
Chandler Carruth	4c727853ed	Fix yet another issue introduced when renaming '-ccc-host-triple' to ... '-target'. The original flag was part of a flag group that marked it as driver-only. The new flag didn't ever get equivalent treatment. This caused the '-target' flag to get passed down to any raw GCC invocation. Marking it as a driver option fixes this and PR11875. llvm-svn: 149244	2012-01-30 12:25:35 +00:00