| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
We don't want to deviate from clang's standard terminology.
llvm-svn: 204997
|
| |
|
|
|
|
|
|
|
| |
bottom of the interface to make it easier to scan and find the public
API.
No functionality changed.
llvm-svn: 204996
|
| |
|
|
|
|
|
| |
out-of-line private static method and into the collection of inline
alignment helpers in MathExtras.h.
llvm-svn: 204995
|
| |
|
|
| |
llvm-svn: 204994
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BumpPtrAllocator significantly less strange by making it a simple
function of the number of slabs allocated rather than by making it
a recurrance. I *think* the previous behavior was essentially that the
size of the slabs would be doubled after the first 128 were allocated,
and then doubled again each time 64 more were allocated, but only if
every allocation packed perfectly into the slab size. If not, the wasted
space wouldn't be counted toward increasing the size, but allocations
over the size threshold *would*. And since the allocations over the size
threshold might be much larger than the slab size, this could have
somewhat surprising consequences where we rapidly grow the slab size.
This currently requires adding state to the allocator to track the
number of slabs currently allocated, but that isn't too bad. I'm
planning further changes to the allocator that will make this state fall
out even more naturally.
It still doesn't fully decouple the growth rate from the allocations
which are over the size threshold. That fix is coming later.
This specific fix will allow making the entire thing into a more
stateless device and lifting the parameters into template parameters
rather than runtime parameters.
llvm-svn: 204993
|
| |
|
|
|
|
|
|
| |
top of the default jit memory manager. This will allow them to be used
as template parameters rather than runtime parameters in a subsequent
commit.
llvm-svn: 204992
|
| |
|
|
| |
llvm-svn: 204991
|
| |
|
|
| |
llvm-svn: 204990
|
| |
|
|
| |
llvm-svn: 204989
|
| |
|
|
|
|
|
| |
These classes are declared in a .cpp file but not used in the same compliation
unit. They seems to have been copy-and-pasted from ELFReader.h.
llvm-svn: 204988
|
| |
|
|
| |
llvm-svn: 204987
|
| |
|
|
| |
llvm-svn: 204986
|
| |
|
|
|
|
|
| |
This should fix the clang-cl tests after the Windows target triple
canonicalization (r204978)
llvm-svn: 204985
|
| |
|
|
| |
llvm-svn: 204984
|
| |
|
|
|
|
|
|
|
| |
* Use assignment instead of swap (since the original value is being
destroyed anyway)
* Rename "updateAdjEdgeId" to "setAdjEdgeId"
llvm-svn: 204983
|
| |
|
|
| |
llvm-svn: 204982
|
| |
|
|
| |
llvm-svn: 204981
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As explained in r204976, because of how the allocation of VSX registers
interacts with the call-lowering code, we sometimes end up generating self VSX
copies. Specifically, things like this:
%VSL2<def> = COPY %F2, %VSL2<imp-use,kill>
(where %F2 is really a sub-register of %VSL2, and so this copy is a nop)
This adds a small cleanup pass to remove these prior to post-RA scheduling.
llvm-svn: 204980
|
| |
|
|
|
|
|
|
|
| |
for the first time.
Thanks Andy for the discussion.
rdar://16162005
llvm-svn: 204979
|
| |
|
|
|
|
|
|
|
| |
This follows the LLVM change to canonicalise the Windows target triple
spellings. Rather than treating each Windows environment as a single entity,
the environments are now modelled properly as an environment. This is a
mechanical change to convert the triple use to reflect that change.
llvm-svn: 204978
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Construct a uniform Windows target triple nomenclature which is congruent to the
Linux counterpart. The old triples are normalised to the new canonical form.
This cleans up the long-standing issue of odd naming for various Windows
environments.
There are four different environments on Windows:
MSVC: The MS ABI, MSVCRT environment as defined by Microsoft
GNU: The MinGW32/MinGW32-W64 environment which uses MSVCRT and auxiliary libraries
Itanium: The MSVCRT environment + libc++ built with Itanium ABI
Cygnus: The Cygwin environment which uses custom libraries for everything
The following spellings are now written as:
i686-pc-win32 => i686-pc-windows-msvc
i686-pc-mingw32 => i686-pc-windows-gnu
i686-pc-cygwin => i686-pc-windows-cygnus
This should be sufficiently flexible to allow us to target other windows
environments in the future as necessary.
llvm-svn: 204977
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because of how the allocation of VSX registers interacts with the call-lowering
code, we sometimes end up generating self VSX copies. Specifically, things like
this:
%VSL2<def> = COPY %F2, %VSL2<imp-use,kill>
(where %F2 is really a sub-register of %VSL2, and so this copy is a nop)
The problem is that ExpandPostRAPseudos always assumes that *some* instruction
has been inserted, and adds implicit defs to it. This is a problem if no copy
was inserted because it can cause subtle problems during post-RA scheduling.
These self copies will have to be removed some other way.
llvm-svn: 204976
|
| |
|
|
|
|
| |
<rdar://problem/16349536>
llvm-svn: 204975
|
| |
|
|
|
|
| |
results, some still have link errors.
llvm-svn: 204974
|
| |
|
|
|
|
|
| |
This reverts commit r204964 because it disabled "= delete", "constexpr"
and "explicit" on GCC.
llvm-svn: 204973
|
| |
|
|
|
|
|
|
| |
in my previous commit (r204884).
<rdar://problem/16381225>
llvm-svn: 204972
|
| |
|
|
|
|
|
|
|
| |
First, v2f64 vector extract had not been declared legal (and so the existing
patterns were not being used). Second, the patterns for that, and for
scalar_to_vector, should really be a regclass copy, not a subregister
operation, because the VSX registers directly hold both the vector and scalar data.
llvm-svn: 204971
|
| |
|
|
| |
llvm-svn: 204970
|
| |
|
|
| |
llvm-svn: 204969
|
| |
|
|
|
|
| |
with non-MSVC compilers.
llvm-svn: 204968
|
| |
|
|
| |
llvm-svn: 204967
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we use both layout-after and layout-before edges to specify atom
orders in the resulting executable. We have a complex piece of code in
LayoutPass.cpp to deal with both types of layout specifiers.
(In the following description, I denote "Atom A having a layout-after edge
to B" as "A -> B", and A's layout-before to B as "A => B".)
However, that complexity is not really needed for this reason: If there
are atoms such that A => B, B -> A is always satisifed, so using only layout-
after relationships will yield the same result as the current code.
Actually we have a piece of complex code that verifies that, for each A -> B,
B => [ X => Y => ... => Z => ] A is satsified, where X, Y, ... Z are all
zero-size atoms. We can get rid of the code from our codebase because layout-
before is basically redundant.
I think we can simplify the code for layout-after even more than this, but
I want to just remove this pass for now for simplicity.
Layout-before edges are still there for dead-stripping, so this change won't
break it. We will remove layout-before in a followup patch once we fix the
dead-stripping pass.
Differential Revision: http://llvm-reviews.chandlerc.com/D3164
llvm-svn: 204966
|
| |
|
|
|
|
|
| |
an opt-in option under -Wselector-type-mismatch.
// rdar://16445728
llvm-svn: 204965
|
| |
|
|
|
|
|
|
| |
Summary: Checking the experimental flag for C++0x is no longer needed.
Differential Revision: http://llvm-reviews.chandlerc.com/D3206
llvm-svn: 204964
|
| |
|
|
|
|
|
|
| |
These operations need to be expanded during legalization so that isel does not
crash. In theory, we might be able to custom lower some of these. That,
however, would need to be follow-up work.
llvm-svn: 204963
|
| |
|
|
|
|
|
|
| |
No functionality change. Thanks Andy for reviewing.
rdar://16162005
llvm-svn: 204962
|
| |
|
|
| |
llvm-svn: 204961
|
| |
|
|
| |
llvm-svn: 204960
|
| |
|
|
|
|
| |
Also, while I'm here, support -nocompress-debug-sections too.
llvm-svn: 204959
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) When creating a .debug_* section and instead create a .zdebug_
section.
2) When creating a fragment in a .zdebug_* section, make it a compressed
fragment.
3) When computing the size of a compressed section, compress the data
and use the size of the compressed data.
4) Emit the compressed bytes.
Also, check that only if a section has a compressed fragment, then that
is the only fragment in the section.
Assert-fail if the fragment's data is modified after it is compressed.
Initial review on llvm-commits by Eric Christopher and Rafael Espindola.
llvm-svn: 204958
|
| |
|
|
| |
llvm-svn: 204957
|
| |
|
|
| |
llvm-svn: 204956
|
| |
|
|
| |
llvm-svn: 204955
|
| |
|
|
|
|
|
|
| |
This commit also adds an additional test case for the global destructor warning.
Reviewed in http://llvm-reviews.chandlerc.com/D3205
llvm-svn: 204954
|
| |
|
|
|
|
|
|
| |
irrelevant
Reviewed in http://llvm-reviews.chandlerc.com/D3190
llvm-svn: 204953
|
| |
|
|
|
|
|
|
| |
Replaces the tablegen-driven AttrSpellings.inc, which lived in the lexing layer with AttrHasAttributeImpl.inc, which lives in the basic layer. Updates the preprocessor to call through to this new functionality which can take additional information into account (such as scopes and syntaxes).
Expose the ability for parts of the compiler to ask whether an attribute is supported for a given spelling (including scope), syntax, triple and language options.
llvm-svn: 204952
|
| |
|
|
|
|
|
|
| |
declarations
Reviewed in http://llvm-reviews.chandlerc.com/D3102
llvm-svn: 204951
|
| |
|
|
|
|
|
| |
Now correctly formats:
foo<true && false>();
llvm-svn: 204950
|
| |
|
|
|
|
| |
for a subprogram DIE.
llvm-svn: 204949
|
| |
|
|
|
|
|
|
|
| |
Fixes a miscompile introduced in r204912. It would miscompile code like
(unsigned)(a + -49) <= 5U. The transform would turn this into
(unsigned)a < 55U, which would return true for values in [0, 49], when
it should not.
llvm-svn: 204948
|