| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 252981
|
|
|
|
|
|
|
|
|
|
| |
commands are running through a range "
- Revert because this commit introduce several failures in lldb test suite
- http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/8391
- This reverts commit 78943bb678c2893703ee4e8b41969372740c8a6f.
llvm-svn: 252980
|
|
|
|
| |
llvm-svn: 252979
|
|
|
|
| |
llvm-svn: 252978
|
|
|
|
| |
llvm-svn: 252977
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D14290
llvm-svn: 252976
|
|
|
|
| |
llvm-svn: 252975
|
|
|
|
|
|
|
|
|
|
| |
It made it possible to apply the memory folding optimization for the 2nd
operand of FMA*_Int instructions.
Reviewer: Quentin Colombet
Differential Revision: http://reviews.llvm.org/D14550
llvm-svn: 252973
|
|
|
|
|
|
|
|
| |
targeting win32.
I will remove REQUIRES later.
llvm-svn: 252972
|
|
|
|
| |
llvm-svn: 252971
|
|
|
|
| |
llvm-svn: 252970
|
|
|
|
|
|
| |
new-value producer usage.
llvm-svn: 252969
|
|
|
|
|
|
| |
parsed.
llvm-svn: 252968
|
|
|
|
|
|
| |
due to ambiguity.
llvm-svn: 252967
|
|
|
|
|
|
| |
We need to add -fPIC to the flags for the builtins in case PIC was turned off at a higher level. We also want to set ENABLE_PIC to Off when building the macho_embedded builtins so the top-level settings don't impact that build.
llvm-svn: 252966
|
|
|
|
| |
llvm-svn: 252965
|
|
|
|
| |
llvm-svn: 252964
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
running through a range
of addresses, and the range has no branches, instead of running to the last instruction and
single-stepping over that, run to the first instruction after the end of the range. If there
are no branches in the current range, then the bytes right after it have to be in the current
function, and have to be instructions not data in code, so this is safe. And it cuts down one
extra stepi per source range step.
Incidentally, this also works around a bug in the llvm Intel assembler where it treats the "rep"
prefix as a separate instruction from the repeated instruction. If that were at the end of a
line range, then we would put a trap in place of the repeated instruction, which is undefined
behavior. Current processors just ignore the repetition in this case, which changes program behavior.
Since there would never be a line range break after the rep prefix, always doing the range stepping
to the beginning of the new range avoids this problem.
<rdar://problem/23461686>
llvm-svn: 252963
|
|
|
|
| |
llvm-svn: 252962
|
|
|
|
| |
llvm-svn: 252961
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
declarations in redeclaration lookup. A declaration is now visible to
lookup if:
* It is visible (not in a module, or in an imported module), or
* We're doing redeclaration lookup and it's externally-visible, or
* We're doing typo correction and looking for unimported decls.
We now support multiple modules having different internal-linkage or no-linkage
definitions of the same name for all entities, not just for functions,
variables, and some typedefs. As previously, if multiple such entities are
visible, any attempt to use them will result in an ambiguity error.
This patch fixes the linkage calculation for a number of entities where we
previously didn't need to get it right (using-declarations, namespace aliases,
and so on). It also classifies enumerators as always having no linkage, which
is a slight deviation from the C++ standard's definition, but not an observable
change outside modules (this change is being discussed on the -core reflector
currently).
This also removes the prior special case for tag lookup, which made some cases
of this work, but also led to bizarre, bogus "must use 'struct' to refer to type
'Foo' in this scope" diagnostics in C++.
llvm-svn: 252960
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DR407, the C++ standard doesn't really say how this should work. Here's what we
do (which is consistent with DR407 as far as I can tell):
* When performing name lookup for an elaborated-type-specifier, a tag
declaration hides a typedef declaration that names the same type.
* When performing any other kind of lookup, a typedef declaration hides
a tag declaration that names the same type.
In any other case where lookup finds both a typedef and a tag (that is, when
they name different types), the lookup will be ambiguous. If lookup finds a
tag and a typedef that name the same type, and finds anything else, the lookup
will always be ambiguous (even if the other entity would hide the tag, it does
not also hide the typedef).
llvm-svn: 252959
|
|
|
|
| |
llvm-svn: 252958
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This failed to solve the problem it was aimed at, and introduced just as many
issues as it resolved. Realistically, we need to deal with the possibility that
multiple modules might define different internal linkage symbols with the same
name, and this isn't a problem unless two such symbols are simultaneously
visible.
The case where two modules define equivalent internal linkage symbols is
handled by r252063: if lookup finds multiple sufficiently-similar entities from
different modules, we just pick one of them as an extension (but we keep them
separate).
llvm-svn: 252957
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit r252565.
This also includes the revert of the commit mentioned below in order to
avoid breaking tests in AMDGPU:
Revert "AMDGPU: Set isAllocatable = 0 on VS_32/VS_64"
This reverts commit r252674.
llvm-svn: 252956
|
|
|
|
|
|
| |
From a patch by Nicholas Allegra!
llvm-svn: 252955
|
|
|
|
|
|
| |
Trace when thread is waiting at join phase for oncore children.
llvm-svn: 252954
|
|
|
|
| |
llvm-svn: 252953
|
|
|
|
|
|
|
|
| |
Fix ittnotify loop metadata reporting for schedule(runtime) and
chunked schedule set via OMP_SCHEDULE. The bug was that chunk=1
reported always.
llvm-svn: 252952
|
|
|
|
|
|
| |
It broke some of the bots including clang-x64-ninja-win7.
llvm-svn: 252951
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D14591
llvm-svn: 252950
|
|
|
|
|
|
|
|
|
|
|
|
| |
rules using table-gen. NFC.
This commit adds new classes CompatRule and MergeRule to Attributes.td,
which are used to generate code to check attribute compatibility and
merge attributes of the caller and callee.
rdar://problem/19836465
llvm-svn: 252949
|
|
|
|
|
|
|
|
|
|
|
| |
r243347 was intended to support a change to LSR (r243348). That change
to LSR has since had to be reverted (r243939) because it was buggy, and
now the code added in r243347 is untested and unexercised. Given that,
I think it is appropriate to revert r243347 for now, with the intent of
adding it back in later if I get around to checking in a fixed version
of r243348.
llvm-svn: 252948
|
|
|
|
| |
llvm-svn: 252947
|
|
|
|
|
|
| |
This will make later functional changes easier to follow.
llvm-svn: 252946
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D14624
llvm-svn: 252945
|
|
|
|
| |
llvm-svn: 252943
|
|
|
|
| |
llvm-svn: 252942
|
|
|
|
|
|
|
|
|
| |
Only when we check for wrapping we want to use the store size, for all
other cases we use the alloc size now.
Suggested by: Tobias Grosser <tobias@grosser.es>
llvm-svn: 252941
|
|
|
|
| |
llvm-svn: 252940
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This finishes the effort to port python-wrapper.swig code over to
using PythonDataObjects.
Also included in this patch is the removal of `PyCallable` from
`python-wrapper.swig`, as it is no longer used after having been
replaced by `PythonCallable` everywhere.
There might be additional cleanup as followup patches, but it should
be all fairly simple and minor.
llvm-svn: 252939
|
|
|
|
|
|
| |
This reverts 252919 which broke LNT: MultiSource/Applications/SPASS
llvm-svn: 252936
|
|
|
|
| |
llvm-svn: 252935
|
|
|
|
| |
llvm-svn: 252934
|
|
|
|
|
|
| |
Differential Revision: http://reviews.llvm.org/D14589
llvm-svn: 252933
|
|
|
|
|
|
|
|
|
| |
Update the ThinLTO function importing test to use DAG forms of checks so
that it is more tolerant of changes to relative ordering between
imported decls/defs. This reduces the number of changes required by the
comdat importing patch I am sending for review shortly.
llvm-svn: 252932
|
|
|
|
|
|
| |
Found by leaksanitizer.
llvm-svn: 252931
|
|
|
|
|
|
| |
Android libc is missing rand_r until API 21. ASan supports API 19.
llvm-svn: 252930
|
|
|
|
|
|
| |
I was a little too aggressive about adding sources from the arm subdirectory.
llvm-svn: 252929
|
|
|
|
|
|
| |
Turns out you need to save before committing.
llvm-svn: 252928
|