| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
llvm-svn: 243311
|
| |
|
|
|
|
|
| |
After r243308, the front-end is responsible for checking the target OS and
passing reserve-x18 if the target is Darwin.
llvm-svn: 243310
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The 3DNOW/PRFCHW cpu targets define both the PREFETCHW (set cache line modified) and PREFETCH (set cache line exclusive) instructions but only the _m_prefetchw (PREFETCHW) intrinsic is included in the header. This patch adds the missing _m_prefetch intrinsic.
I'm basing this off AMD documentation - the intel docs on the support for PREFETCHW isn't clear whether Silvermont/Broadwell properly support PREFETCH but given that the intrinsic implementation is a default __builtin_prefetch call, it is safe whatever.
Fix for PR23648
Differential Revision: http://reviews.llvm.org/D11338
llvm-svn: 243305
|
| |
|
|
| |
llvm-svn: 243292
|
| |
|
|
|
|
| |
instruction.
llvm-svn: 243289
|
| |
|
|
| |
llvm-svn: 243285
|
| |
|
|
|
|
| |
attempt to fix regressions triggered by r243277.
llvm-svn: 243280
|
| |
|
|
|
|
|
|
|
| |
Also rename XCore (the toolchain) to XCoreToolChain since XCore is
also a namespace for its tools.
Differential Revision: http://reviews.llvm.org/D10609
llvm-svn: 243279
|
| |
|
|
|
|
| |
if TLS is enabled in OpenMP code generation.
llvm-svn: 243277
|
| |
|
|
|
|
| |
Patch by Vedant Kumar!
llvm-svn: 243275
|
| |
|
|
|
|
|
|
|
|
| |
Currently trigger to select hard-float linker is only based of -gnueabihf
appearing in target triplet, but we should also select it when hardfloat
is requested via cmdline.
Patch by Khem Raj.
llvm-svn: 243262
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had multiple bugs here:
- We didn't support multiple optimization options in one argument.
e.g. -O2y-
- We didn't correctly expand -O[12dx] to their respective options.
- We treated -O1 as clang -O1 instead of clang -Os.
- We treated -Ox as clang -O3 instead of clang -O2. In fact, cl's -Ox
option is *less* powerful than cl's -O2 option despite -Ox described
as "Full Optimization".
This fixes PR24003.
llvm-svn: 243261
|
| |
|
|
|
|
|
|
|
| |
isWhitespaceExceptNL. If that's wasn't bad enough, we have an identically
named function in Basic/CharInfo.h.
While at it, remove unnecessary includes, .str() calls and #ifdef.
llvm-svn: 243260
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chain and fix the cases where it fires.
* Handle the __va_list_tag as a predefined decl. Previously we failed to merge
sometimes it because it's not visible to name lookup. (In passing, remove
redundant __va_list_tag typedefs that we were creating for some ABIs. These
didn't affect the mangling or representation of the type.)
* For Decls derived from Redeclarable that are not in fact redeclarable
(implicit params, function params, ObjC type parameters), remove them from
the list of expected redeclarable decls.
llvm-svn: 243259
|
| |
|
|
|
|
| |
We used to define them to 1, we should have defined them to 100.
llvm-svn: 243255
|
| |
|
|
|
|
| |
These cases should now be impossible as of r243243.
llvm-svn: 243252
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There is currently no support in MSVC for using i128 as an integer
literal suffix. In fact, there appears to be no evidence that they have
ever supported this feature in any of their compilers. This was an over
generalization of their actual feature and is a nasty source of bugs.
Why is it a source of bugs? Because most code in clang expects that
evaluation of an integer constant expression won't give them something
that 'long long' can't represent. Instead of providing a meaningful
feature, i128 gives us cute ways of exploding the compiler.
llvm-svn: 243243
|
| |
|
|
|
|
| |
No functionality change intended, just a tidy-up.
llvm-svn: 243242
|
| |
|
|
|
|
|
| |
We could probably get this and the previous three disabled in r243237
working on these builders if MSYS was updated to current MSYS2.
llvm-svn: 243238
|
| |
|
|
| |
llvm-svn: 243237
|
| |
|
|
| |
llvm-svn: 243236
|
| |
|
|
| |
llvm-svn: 243235
|
| |
|
|
|
|
|
| |
This test was missing a triple causing it to error out on windows
targets. They accept a much smaller alignment value.
llvm-svn: 243234
|
| |
|
|
|
|
|
| |
Don't use the spelling of the alignment attribute to determine whether
or not an alignment amount makes sense.
llvm-svn: 243233
|
| |
|
|
|
|
|
| |
This boilerplate code was necessary to move arguments between threads in
C++98, lambdas make this much easier. No functionality change intended.
llvm-svn: 243227
|
| |
|
|
|
|
|
| |
RecordLayoutBuilder is an inaccruate name because it does not build all
records. It only builds layouts for targets using the Itanium C++ ABI.
llvm-svn: 243225
|
| |
|
|
|
|
| |
At least on my mingw system they do pass, let's see what the bots think.
llvm-svn: 243224
|
| |
|
|
| |
llvm-svn: 243222
|
| |
|
|
|
|
| |
No functional change intended.
llvm-svn: 243221
|
| |
|
|
| |
llvm-svn: 243218
|
| |
|
|
|
|
|
|
|
| |
This lets us pass functors (and lambdas) without void * tricks. On the
downside we can't pass CXXRecordDecl's Find* members (which are now type
safe) to lookupInBases directly, but a lambda trampoline is a small
price to pay. No functionality change intended.
llvm-svn: 243217
|
| |
|
|
|
|
|
| |
Avoids the awkward passing of an opaque void *UserData argument. No
functional change intended.
llvm-svn: 243213
|
| |
|
|
| |
llvm-svn: 243207
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
__builtin_frame_address requires its argument to be a constant
expression which already implies that it cannot have undefined behavior.
However, we used EmitScalarExpr to emit the argument causing UBSan to
try to check for overflow.
Instead, use the constant expression emission system.
This fixes PR24256.
llvm-svn: 243206
|
| |
|
|
|
|
|
|
| |
This fixes the clang crash reported in PR24000.
Differential Revision: http://reviews.llvm.org/D11341
llvm-svn: 243196
|
| |
|
|
|
|
|
| |
This is a follow-up to r243185, which made changes to pass subtarget
feature "+reserve-x18" instead of backend option "-aarch64-reserve-x18".
llvm-svn: 243189
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
option "-aarch64-reserve-x18".
This change is needed since backend options do not make it to the backend
when doing LTO and are not capable of changing the behavior of code-gen
passes on a per-function basis.
rdar://problem/21529937
Differential Revision: http://reviews.llvm.org/D11462
llvm-svn: 243185
|
| |
|
|
|
|
| |
the wording is identical; NFC.
llvm-svn: 243169
|
| |
|
|
|
|
|
|
|
| |
Change `getOrCreateLimitedType()` to return a `DICompositeType` and
remove the casts from its callers. Inside, I've strengthened a `cast`
from `DICompositeTypeBase`, but the casts in the callers already prove
that this is safe. There should be no functionality change here.
llvm-svn: 243155
|
| |
|
|
|
|
|
|
| |
Generic_GCC::GCCVersion
similar to the way Generic_GCC::GCCInstallationDetector::ScanLibDirForGCCTriple works.
llvm-svn: 243153
|
| |
|
|
|
|
| |
Thanks to Richard Smith for pointing this out!
llvm-svn: 243144
|
| |
|
|
|
|
|
|
|
|
| |
These changes are for Android x86_64 targets to be compatible with current Android g++.
https://llvm.org/bugs/show_bug.cgi?id=23897
Use 'g' and 'Cg' for "long double" and "long double _Complex" mangled type names.
Differential Revision: http://reviews.llvm.org/D11466
llvm-svn: 243133
|
| |
|
|
|
|
|
| |
Change `StaticDataMemberCache` to store references to `DIDerivedType`
directly, and remove now-unnecessary casts from the accessors.
llvm-svn: 243129
|
| |
|
|
| |
llvm-svn: 243125
|
| |
|
|
| |
llvm-svn: 243120
|
| |
|
|
|
|
|
|
|
|
|
|
| |
implementations.
The outer nullability is transferred from the declaration to the implementation so including them is redundant.
The inner ones are not transferred so they are kept to match the exact types. When we transfer the inner ones as well
adding them in the implementation will become redundant and we should strip those as well.
rdar://21737451
llvm-svn: 243119
|
| |
|
|
|
| |
From: Mehdi Amini <mehdi.amini@apple.com>
llvm-svn: 243115
|
| |
|
|
|
|
| |
not throughUsingDeclaration(). (2) Testing shows that this does work for shadowed variables as well as shadowed functions. I could not find an example where this matcher was failing. NFC.
llvm-svn: 243111
|
| |
|
|
|
|
| |
also silence a -Wreturn-type warning. NFC intended.
llvm-svn: 243109
|
| |
|
|
|
|
| |
a compile error.
llvm-svn: 243108
|