| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
to delete result files for only those commands that fail.
Part of rdar://12984531
llvm-svn: 173361
|
| |
|
|
|
|
| |
inline assembly can be enable with -fasm-blocks or -fms-extensions alone.
llvm-svn: 173186
|
| |
|
|
|
|
| |
don't require executable to be linked with UBSan.' to Mac
llvm-svn: 173014
|
| |
|
|
|
|
| |
AddressSanitizer use bottom of the address space for the shadow memory. On Linux it can be used with -fPIE/-pie to improve performance.
llvm-svn: 172974
|
| |
|
|
|
|
| |
the executable to be linked with UBSan.
llvm-svn: 172856
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AT_producer. Which includes clang's version information so we can tell
which version of the compiler was used.
This is second of the two steps to allow us to do this. The first was a
change to llvm-mc with revision 172630 to provide a method to set the
AT_producer string. This second step has the clang driver passing the value
of getClangFullVersion() via the new flag -dwarf-debug-producer when invoking
the integrated assembler on assembly source files. Then using the new
setDwarfDebugProducer() method to set the AT_producer string.
rdar://12888242
llvm-svn: 172758
|
| |
|
|
|
|
|
| |
the gcc driver and makes it possible to add -pie to $CC or similar and
have it apply in the right places.
llvm-svn: 172753
|
| |
|
|
|
|
|
|
|
|
|
| |
-fopenmp in the link step on Linux. There is probably more tweaking that
will need to take place to get good support for linking the relevant
libraries on all Linux distributions and/or on other platforms, but this
get's the ball moving and allows Clang to build programs which contain
OpenMP pragmas that can be safely ignored by a compiler that doesn't
implement them, and yet makes direct calls into the OpenMP runtime.
llvm-svn: 172715
|
| |
|
|
| |
llvm-svn: 172605
|
| |
|
|
|
|
| |
users can explicitly enable/disable modules autolinking.
llvm-svn: 172592
|
| |
|
|
|
|
|
|
|
|
| |
flag information down from the Clang driver into the Gold linker plugin
for LTO. This allows specifying -march on the linker commandline and
should hopefully have it pass all the way through to the LTO optimizer.
Fixes PR14697.
llvm-svn: 172354
|
| |
|
|
|
|
| |
the backend if hard float ABI is selected under -mips16 mode.
llvm-svn: 172062
|
| |
|
|
|
|
| |
Patch by Brad Smith.
llvm-svn: 171329
|
| |
|
|
| |
llvm-svn: 171264
|
| |
|
|
| |
llvm-svn: 171020
|
| |
|
|
| |
llvm-svn: 170909
|
| |
|
|
| |
llvm-svn: 170472
|
| |
|
|
|
|
|
|
| |
for location information.
Part of PR14624
llvm-svn: 170391
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also requires adding support to -cc1as for passing the detecting
PWD down through LLVM's debug info (which in turn required the LLVM
change in r170371).
The test case is weak (we only test the driver behavior) because there
is currently to infrastructure for running cc1as in the test suite. So
those four lines are untested (much like all other lines in that file),
but we have a test for the same pattern using llvm-mc in the LLVM
repository.
llvm-svn: 170373
|
| |
|
|
|
|
| |
Patch by Andrew Turner.
llvm-svn: 170096
|
| |
|
|
|
|
| |
rdar://12851905
llvm-svn: 170010
|
| |
|
|
|
|
|
|
|
|
|
| |
Add -fslp-vectorize (with -ftree-slp-vectorize as an alias for gcc compatibility)
to provide a way to enable the basic-block vectorization pass. This uses the same
acronym as gcc, superword-level parallelism (SLP), also common in the literature,
to refer to basic-block vectorization.
Nadav suggested this as a follow-up to the adding of -fvectorize.
llvm-svn: 169909
|
| |
|
|
|
|
| |
rdar://12839978
llvm-svn: 169885
|
| |
|
|
| |
llvm-svn: 169775
|
| |
|
|
| |
llvm-svn: 169611
|
| |
|
|
|
|
| |
compatibility
llvm-svn: 169599
|
| |
|
|
|
|
| |
threshold, pic, pie
llvm-svn: 169517
|
| |
|
|
|
|
|
|
| |
linker directly
Rather than calling gcc.
llvm-svn: 169512
|
| |
|
|
|
|
|
|
|
|
|
|
| |
ToolChains.cpp
This is in anticipation of forthcoming library path changes.
Also ...
- Fixes some inconsistencies in how the arch is passed to tools.
- Add test cases for various forms of arch flags
llvm-svn: 169505
|
| |
|
|
|
|
|
|
|
|
| |
paths
- Inherit from Linux rather than ToolChain
- Override AddClangSystemIncludeArgs and AddClangCXXStdlibIncludeArgs
to properly set include paths.
llvm-svn: 169495
|
| |
|
|
|
|
|
| |
-fasm-blocks flag, not the -fms-extensions flag.
rdar://12808010
llvm-svn: 169422
|
| |
|
|
|
|
|
| |
Add a diagnosting for -fsanitize=memory conflicting with other sanitizers.
Extend tests.
llvm-svn: 169380
|
| |
|
|
|
|
|
|
|
|
|
| |
This ensures that even though it comes first, we pick up its .o files.
Note that if we can use this (or something similar / equivalent) on
other platforms, we could potentially remove
ReplaceOperatorsNewAndDelete from the ASan runtimes.
We should probably do something similar for TSan and MSan as well.
llvm-svn: 169328
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the link command. This all works fine when the driver is also responsible for
adding -lstdc++ to the link command. But, if -lstdc++ (or libstdc++.a, etc) is
passed explicitly to the driver, the ASan runtime will appear in the link
command after the standard library, leading to multiple-definition errors for
the global 'operator new' and 'operator delete'. Fix this in a painfully
simple way, by inserting libclang_rt.asan.a at the start of the link command
instead of the end.
If we need to do something more clever, we can walk the link command looking
for something that resembles libstdc++ and insert libclang_rt.asan.a as late
as possible, but the simple solution works for now.
llvm-svn: 169310
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
uncovered.
This required manually correcting all of the incorrect main-module
headers I could find, and running the new llvm/utils/sort_includes.py
script over the files.
I also manually added quite a few missing headers that were uncovered by
shuffling the order or moving headers up to be main-module-headers.
llvm-svn: 169237
|
| |
|
|
|
|
| |
flag usable for ASan. Blacklisting can be used to disable sanitizer checks for particular file/function/object.
llvm-svn: 169144
|
| |
|
|
| |
llvm-svn: 169124
|
| |
|
|
|
|
| |
to enable/disable support of GOT larger than 64k.
llvm-svn: 169098
|
| |
|
|
|
|
| |
a while.
llvm-svn: 169066
|
| |
|
|
| |
llvm-svn: 168958
|
| |
|
|
| |
llvm-svn: 168956
|
| |
|
|
| |
llvm-svn: 168953
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
features of ASan:
1) init-order sanitizer: initialization-order checker.
Status: usable, but may produce false positives w/o proper blacklisting.
2) use-after-return sanitizer
Status: implemented, but heavily understed.
Should be optional, as it significanlty slows program down.
3) use-after-scope sanitizer
Status: in progress.
llvm-svn: 168950
|
| |
|
|
|
|
| |
before libstdc++ like we do with ubsan.
llvm-svn: 168918
|
| |
|
|
|
|
| |
rdar://12771737
llvm-svn: 168841
|
| |
|
|
|
|
| |
diagnostic for invalid sets of sanitizers
llvm-svn: 168794
|
| |
|
|
| |
llvm-svn: 168510
|
| |
|
|
|
|
|
|
|
|
|
| |
Unlike my previous attempt at this, this patch leaves intact the check for
whether clang can handle the input file type, and for non-Darwin toolchains it
will invoke gcc for things it cannot handle. For Darwin toolchains, the
behavior reported in pr14338 still occurs with this patch, but that is a
definite improvement from what happens currently, where it just crashes with
an assertion failure.
llvm-svn: 168505
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, this flag to CC1 was never exposed at the clang driver
layer, and if you happened to enable it (by being on Android or GCC 4.7
platform), you couldn't *disable* it, because there was no 'no' variant.
The whole thing was confusingly implemented.
Now, the target-specific flag processing gets the driver arg list, and
we use standard hasFlag with a default based on the GCC version and/or
Android platform. The user can still pass the 'no-' variant to forcibly
disable the flag, or pass the positive variant to clang itself to enable
the flag.
The test has also been substantially cleaned up and extended to cover
these use cases.
llvm-svn: 168473
|
| |
|
|
|
|
|
|
|
|
|
| |
According to Android ABI, we have to link with
libdl.so, if we are linking with non-static libgcc.
Besides, this also fixes MIPS link error of
undefined references to `_Unwind_Find_FDE' and
`dl_iterate_phdr'.
llvm-svn: 168310
|