| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One unusual feature of the z architecture is that the result of a
previous load can be reused indefinitely for subsequent loads, even if
a cache-coherent store to that location is performed by another CPU.
A special serializing instruction must be used if you want to force
a load to be reattempted.
Since volatile loads are not supposed to be omitted in this way,
we should insert a serializing instruction before each such load.
The same goes for atomic loads.
The patch implements this at the IR->DAG boundary, in a similar way
to atomic fences. It is a no-op for targets other than SystemZ.
llvm-svn: 196905
|
|
|
|
| |
llvm-svn: 196904
|
|
|
|
| |
llvm-svn: 196903
|
|
|
|
|
|
| |
It depends on nothing described in LLVM_LINK_COMPONENTS.
llvm-svn: 196902
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
The rule from the GNU style states:
"We find it easier to read a program when it has spaces before the open-parentheses and after the commas."
http://www.gnu.org/prep/standards/standards.html#index-spaces-before-open_002dparen
This patch makes clang-format adds an option to put spaces before almost all open parentheses, except the cases, where different behavior is dictated by the style rules or language syntax:
* preprocessor:
** function-like macro definitions can't have a space between the macro name and the parenthesis;
** `#if defined(...)` can have a space, but it seems, that it's more frequently used without a space in GCC, for example;
* never add spaces after unary operators;
* adding spaces between two opening parentheses is controlled with the `SpacesInParentheses` option;
* never add spaces between `[` and `(` (there's no option yet).
Reviewers: djasper
Reviewed By: djasper
CC: cfe-commits, klimek
Differential Revision: http://llvm-reviews.chandlerc.com/D2326
llvm-svn: 196901
|
|
|
|
|
|
| |
assumption that the left stack redzone is >= 32 bytes (PR18195)
llvm-svn: 196900
|
|
|
|
| |
llvm-svn: 196898
|
|
|
|
| |
llvm-svn: 196897
|
|
|
|
| |
llvm-svn: 196896
|
|
|
|
|
|
|
| |
Code to create COFF section header was scattered across many member functions
of SectionChunk. Consolidate it to a member function of SectionHeaderTableChunk.
llvm-svn: 196895
|
|
|
|
| |
llvm-svn: 196894
|
|
|
|
| |
llvm-svn: 196893
|
|
|
|
|
|
|
|
|
| |
more than one such initializer in a union, make mem-initializers override
default initializers for other union members, handle anonymous unions with
anonymous struct members better. Fix a couple of semi-related bugs exposed by
the tests for same.
llvm-svn: 196892
|
|
|
|
| |
llvm-svn: 196891
|
|
|
|
|
|
| |
... because they are used only in the function for relocations.
llvm-svn: 196890
|
|
|
|
|
|
| |
This is a small change to be strict. Just want get pattern safer.
llvm-svn: 196889
|
|
|
|
| |
llvm-svn: 196888
|
|
|
|
| |
llvm-svn: 196887
|
|
|
|
| |
llvm-svn: 196884
|
|
|
|
| |
llvm-svn: 196883
|
|
|
|
| |
llvm-svn: 196882
|
|
|
|
|
|
| |
I'll prune redundant deps in LLVMBuild.txt, later.
llvm-svn: 196881
|
|
|
|
| |
llvm-svn: 196880
|
|
|
|
|
|
|
| |
This reverts commit r196876. Its tests failed on the bots, so I'll
figure it out tomorrow.
llvm-svn: 196879
|
|
|
|
|
|
| |
Use of static is recommended by the style guide.
llvm-svn: 196877
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For stack frames requiring realignment, three pointers may be needed:
- ebp to address incoming arguments
- esi (could be any callee-saved register) to address locals
- esp to address outgoing arguments
We would use esi unconditionally without verifying that it did not
conflict with inline assembly.
This change doesn't do the verification, it simply emits a fatal error
on functions that use stack realignment, dynamic SP adjustments, and
inline assembly.
Because stack realignment is common on Windows, we also no longer assume
that MS inline assembly clobbers esp. Instead, we analyze the inline
instructions for implicit definitions and check if esp is there. If so,
we require the use of a base pointer and consider it in the condition
above.
Mostly fixes PR16830, but we could try harder to find a non-conflicting
base pointer.
Reviewers: sunfish
Differential Revision: http://llvm-reviews.chandlerc.com/D1317
llvm-svn: 196876
|
|
|
|
|
|
|
|
|
| |
it to the LLVM project through the appropriate channels.
This reverts:
r195837: "[Sanitizer] Add rudimentary support for using libbacktrace in ..."
llvm-svn: 196875
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MCJIT needs to be able to run in hostile environments, even when PWD
is invalid. There's no need to crash MCJIT in this case.
The obvious fix is to simply leave MCContext's CompilationDir empty
when PWD can't be determined. This way, MCJIT clients,
and other clients that link with LLVM don’t need a valid working directory.
If we do want to guarantee valid CompilationDir, that should be done
only for clients of getCompilationDir(). This is as simple as checking
for an empty string.
The only current use of getCompilationDir is EmitGenDwarfInfo, which
won’t conceivably run with an invalid working dir. However, in the
purely hypothetically and untestable case that this happens, the
AT_comp_dir will be omitted from the compilation_unit DIE.
llvm-svn: 196874
|
|
|
|
| |
llvm-svn: 196873
|
|
|
|
| |
llvm-svn: 196867
|
|
|
|
|
|
|
| |
These member functions are not overriden and not intended to be, so adding
virtual does not make sense.
llvm-svn: 196866
|
|
|
|
|
|
| |
appease FileManager.
llvm-svn: 196865
|
|
|
|
| |
llvm-svn: 196864
|
|
|
|
| |
llvm-svn: 196863
|
|
|
|
| |
llvm-svn: 196862
|
|
|
|
|
|
|
|
| |
In order to address latent bugs that were easier to expose in 64-bit
mode, we move the application of __declspec(align) to before the layout
of vbases rather than after.
llvm-svn: 196861
|
|
|
|
| |
llvm-svn: 196860
|
|
|
|
| |
llvm-svn: 196859
|
|
|
|
| |
llvm-svn: 196858
|
|
|
|
| |
llvm-svn: 196857
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to gcov, llvm-cov will now print out the block count at the end
of each block. Multiple blocks can end on the same line.
One computational difference is by using -a, llvm-cov will no longer
simply add the block counts together to form a line count. Instead, it
will take the maximum of the block counts on that line. This has a
similar effect to what gcov does, but generates more correct counts in
certain scenarios.
Also updated tests.
llvm-svn: 196856
|
|
|
|
|
|
| |
This fixes pr18141.
llvm-svn: 196855
|
|
|
|
|
|
|
|
|
|
|
|
| |
The windows target does not support using an external assembler so
the test case was failing with this error:
error: there is no external assembler that can be used on this platform
The test was updated to always explicitly pass a target that has
both an interal and external assembler.
llvm-svn: 196854
|
|
|
|
|
|
|
| |
This reverts commit r196475 because it made the build to fail with
GCC 4.7/4.8/4.9. Reported by Mikael Lyngvig.
llvm-svn: 196853
|
|
|
|
|
|
|
|
|
|
|
|
| |
The standard is pretty clear on what it allows inside of template
arguments for non-type template parameters of pointer-to-member.
They must be of the form &qualified-id and cannot come from sources like
constexpr VarDecls or things of that nature.
This fixes PR18192.
llvm-svn: 196852
|
|
|
|
| |
llvm-svn: 196851
|
|
|
|
| |
llvm-svn: 196850
|
|
|
|
|
|
| |
empty one.
llvm-svn: 196849
|
|
|
|
| |
llvm-svn: 196848
|
|
|
|
|
|
| |
Thanks to Jim Grosbach for noticing it.
llvm-svn: 196846
|