| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
| |
on the system, and report it when running the driver in verbose mode.
Without this it is essentially impossible to understand why a particular
GCC toolchain is used by Clang for libstdc++, libgcc, etc.
This also required threading a hook through the toolchain layers for
a specific toolchain implementation to print custom information under
'clang -v'. The naming here isn't spectacular. Suggestions welcome.
llvm-svn: 187427
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This establishes a new Flag in Options.td, which can be assigned to
options that should be made available in clang's cl.exe compatible
mode, and updates the Driver to make use of the flag.
(The whitespace change to CMakeLists forces the build to re-run CMake
and pick up the include dependency on the new .td file. This makes the
build work if someone moves backwards in commit history after this change.)
Differential Revision: http://llvm-reviews.chandlerc.com/D1215
llvm-svn: 187280
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch provides basic support for powerpc64le as an LLVM target.
However, use of this target will not actually generate little-endian
code. Instead, use of the target will cause the correct little-endian
built-in defines to be generated, so that code that tests for
__LITTLE_ENDIAN__, for example, will be correctly parsed for
syntax-only testing. Code generation will otherwise be the same as
powerpc64 (big-endian), for now.
The patch leaves open the possibility of creating a little-endian
PowerPC64 back end, but there is no immediate intent to create such a
thing.
The new test case variant ensures that correct built-in defines for
little-endian code are generated.
llvm-svn: 187180
|
|
|
|
| |
llvm-svn: 186970
|
|
|
|
|
|
|
| |
The mode doesn't actually do anything yet, but this provides a
way to get into it.
llvm-svn: 186720
|
|
|
|
| |
llvm-svn: 186617
|
|
|
|
|
|
|
|
|
|
|
|
| |
and add a new option --driver-mode= to control it explicitly.
The CCCIsCXX and CCCIsCPP flags were non-overlapping, i.e. there
are currently really three modes that Clang can run in: gcc, g++
or cpp, so it makes sense to represent them as an enum.
Having a command line flag to control it helps testing.
llvm-svn: 186605
|
|
|
|
| |
llvm-svn: 186487
|
|
|
|
| |
llvm-svn: 186448
|
|
|
|
| |
llvm-svn: 185717
|
|
|
|
|
|
| |
avoid specifying the vector size unnecessarily.
llvm-svn: 185610
|
|
|
|
|
|
|
|
| |
Original message:
Use the new PathV2 instead of implementing the logic in clang.
llvm-svn: 184825
|
|
|
|
|
|
| |
This reverts commit 184803 while I debug the failures on the bots.
llvm-svn: 184818
|
|
|
|
| |
llvm-svn: 184807
|
|
|
|
| |
llvm-svn: 184803
|
|
|
|
| |
llvm-svn: 184774
|
|
|
|
| |
llvm-svn: 184770
|
|
|
|
| |
llvm-svn: 184297
|
|
|
|
| |
llvm-svn: 184090
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The big changes are:
- Deleting Driver/(Arg|Opt)*
- Rewriting includes to llvm/Option/ and re-sorting
- 'using namespace llvm::opt' in clang::driver
- Fixing the autoconf build by adding option everywhere
As discussed in the review, this change includes using directives in
header files. I'll make follow up changes to remove those in favor of
name specifiers.
Reviewers: espindola
Differential Revision: http://llvm-reviews.chandlerc.com/D975
llvm-svn: 183989
|
|
|
|
| |
llvm-svn: 183861
|
|
|
|
|
|
|
|
|
| |
This option is used to select a dynamic loader prefix to be used
at runtime. Currently this is implemented for the Linux toolchain.
Differential Revision: http://llvm-reviews.chandlerc.com/D851
llvm-svn: 182744
|
|
|
|
|
|
|
| |
to the temporary files.
rdar://13218604
llvm-svn: 180813
|
|
|
|
| |
llvm-svn: 178358
|
|
|
|
|
|
| |
toolchain flags for MIPS targets.
llvm-svn: 178232
|
|
|
|
|
|
|
|
|
|
|
| |
information about a particular module file.
This option can be useful for end users who want to know why they
ended up with a ton of different variants of the "std" module in their
module cache. This problem should go away over time, as we reduce the
need for module variants, but it will never go away entirely.
llvm-svn: 178148
|
|
|
|
| |
llvm-svn: 177840
|
|
|
|
|
|
|
|
|
|
|
| |
Changing -ccc-install-dir to affect cc1's resource-dir setting broke our
internal LNT tests. After discussing the situation with Jim, we've decided to
pursue an alternate approach. We really want the resource-dir to be located
relative to clang, even when using -ccc-install-dir, but we're going to
add a fallback setting for the libc++ headers if they don't exist alongside
the compiler.
llvm-svn: 177815
|
|
|
|
|
|
|
|
| |
linker via --dynamic-list instead of using --export-dynamic. This reduces the
size of the dynamic symbol table, and thus of the binary (in some cases by up
to ~30%).
llvm-svn: 177783
|
|
|
|
| |
llvm-svn: 177303
|
|
|
|
|
|
| |
argument.
llvm-svn: 177301
|
|
|
|
| |
llvm-svn: 177299
|
|
|
|
| |
llvm-svn: 177293
|
|
|
|
| |
llvm-svn: 177287
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-ccc-install-dir is supposed to cause the compiler to behave as-if it
were installed in the indicated location. It almost does, but misses
anything that's relying on the resource directory (libc++ header search,
in particular). The resource dir is resolved too early, before command
line args are handled.
The fix is simply to move handling of the resource dir until after we
know if a -ccc-install-dir is present.
rdar://13402696
llvm-svn: 176894
|
|
|
|
|
|
|
|
|
| |
There is now a single function to get the list of phases for a given
output Type.
No functionality change intended.
llvm-svn: 176628
|
|
|
|
| |
llvm-svn: 176128
|
|
|
|
|
|
|
| |
in the compilation setup. Note that this doesn't currently
work for -no-integrated-as.
llvm-svn: 175813
|
|
|
|
| |
llvm-svn: 175418
|
|
|
|
| |
llvm-svn: 175409
|
|
|
|
|
|
| |
the DWARF5 split dwarf proposal.
llvm-svn: 174349
|
|
|
|
|
|
| |
Part of rdar://13134273
llvm-svn: 174203
|
|
|
|
|
|
| |
minor cleanup.
llvm-svn: 173852
|
|
|
|
|
|
|
|
|
|
|
| |
subsequent commands from being executed.
The diagnostics generation isn't designed for this use case, so add a note to
fix this in the very near future. For now, just generated the diagnostics for
the first failing command.
Part of rdar://12984531
llvm-svn: 173825
|
|
|
|
| |
llvm-svn: 173700
|
|
|
|
|
|
|
| |
to delete result files for only those commands that fail.
Part of rdar://12984531
llvm-svn: 173361
|
|
|
|
|
|
|
|
| |
produce a note for that diagnostic either with a different DiagnosticEngine or
after calling DiagnosticEngine::Reset(). That didn't make any sense, and did the
wrong thing if the original diagnostic was suppressed.
llvm-svn: 170636
|
|
|
|
|
|
|
|
| |
llvm::sys::PathSeparator, that is ';' in Win32 hosts.
Thanks to Bogon Kim!
llvm-svn: 169964
|
|
|
|
|
|
|
|
|
|
| |
paths
- Inherit from Linux rather than ToolChain
- Override AddClangSystemIncludeArgs and AddClangCXXStdlibIncludeArgs
to properly set include paths.
llvm-svn: 169495
|
|
|
|
|
|
|
|
| |
prevent llvm-config.h.
Or "llvm/Support/system_error.h" could not be compiled on mingw.
llvm-svn: 169354
|