| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
floats.
llvm-svn: 197592
|
| |
|
|
|
|
| |
A f64 inside a struct can be 32 bit aligned on darwin.
llvm-svn: 197577
|
| |
|
|
|
|
| |
No functionality change.
llvm-svn: 197548
|
| |
|
|
|
|
|
|
| |
This has no functionality change as clang adds explicit alignment info for
byval arguments. The only difference is that now the clang produced
DataLayout string for AArch64 is identical to the LLVM produced one.
llvm-svn: 197538
|
| |
|
|
| |
llvm-svn: 197504
|
| |
|
|
| |
llvm-svn: 197502
|
| |
|
|
|
|
| |
This makes it identical to the string llvm produces.
llvm-svn: 197500
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead, mark the module as unavailable so that clang errors as soon as
someone tries to build this module.
This works towards the long-term goal of not stat'ing the header files at all
while reading the module map and instead read them only when the module is
being built (there is a corresponding FIXME in parseHeaderDecl()). However, it
seems non-trivial to get there and this unblock us and moves us into the right
direction.
Also changed the implementation to reuse the same DiagnosticsEngine.
llvm-svn: 197485
|
| |
|
|
|
|
|
| |
This completes the cleanup/refactoring of DataLayout on the clang side. Next
is figuring out the differences between the llvm and clang produced strings
llvm-svn: 197442
|
| |
|
|
| |
llvm-svn: 197440
|
| |
|
|
| |
llvm-svn: 197437
|
| |
|
|
|
|
| |
I missed these in previous commits.
llvm-svn: 197435
|
| |
|
|
|
|
|
| |
The f80:128:128 was followed by a f80:32:32 and so never used. Looks like this
was there since r91746.
llvm-svn: 197433
|
| |
|
|
| |
llvm-svn: 197430
|
| |
|
|
| |
llvm-svn: 197429
|
| |
|
|
| |
llvm-svn: 197427
|
| |
|
|
| |
llvm-svn: 197422
|
| |
|
|
| |
llvm-svn: 197421
|
| |
|
|
|
|
|
|
|
|
| |
An empty string for an ASM input constraint is invalid, and will crash
during clang CodeGen. Change TargetInfo::validateInputConstraint to
reject an empty string.
<rdar://problem/15552191>
llvm-svn: 197362
|
| |
|
|
|
|
| |
This is always overwritten by the one in NaClTargetInfo.
llvm-svn: 197346
|
| |
|
|
| |
llvm-svn: 197270
|
| |
|
|
| |
llvm-svn: 197268
|
| |
|
|
|
|
| |
They are equivalent and the size of 'a' and 's' is unused.
llvm-svn: 197256
|
| |
|
|
|
|
|
|
| |
target_link_libraries() and LLVM_LINK_COMPONENTS.
I will prune redundant dependencies later.
llvm-svn: 196800
|
| |
|
|
|
|
|
|
| |
We already support using "r" on 64-bit values (a GPRPair is
allocated), but Sema doesn't know this yet so issues a warning. This
should fix it.
llvm-svn: 196724
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- krait processor currently modeled with the same features as A9.
- Krait processor additionally has VFP4 (fused multiply add/sub)
and hardware division features enabled.
- krait has currently the same Schedule model as A9
- krait cpu flag is not recognized by the GNU assembler yet,
it is replaced with march=armv7-a to avoid a lower march
from being used.
llvm-svn: 196618
|
| |
|
|
| |
llvm-svn: 196510
|
| |
|
|
| |
llvm-svn: 196346
|
| |
|
|
| |
llvm-svn: 196115
|
| |
|
|
| |
llvm-svn: 196114
|
| |
|
|
| |
llvm-svn: 195970
|
| |
|
|
| |
llvm-svn: 195563
|
| |
|
|
|
|
| |
Patch by Oliver Stannard!
llvm-svn: 195449
|
| |
|
|
|
|
|
|
|
| |
There seem to be quite a few references to the old macro __ARM_NEON__ on the
internet, so I don't think it's a good idea to remove it entirely (at least
yet), but the canonical name does not have the trailing underscores so we
should use that ourselves.
llvm-svn: 195353
|
| |
|
|
|
|
|
|
|
| |
Make sure armv7 doesn't get the iOS deployment version definitions when
it's being used for non-iOS.
rdar://15497681
llvm-svn: 195149
|
| |
|
|
| |
llvm-svn: 195068
|
| |
|
|
| |
llvm-svn: 195024
|
| |
|
|
| |
llvm-svn: 194751
|
| |
|
|
|
|
|
|
|
|
|
| |
We already have builtins that are only available in GNU mode, so this
mirrors that.
Reviewers: rsmith
Differential Revision: http://llvm-reviews.chandlerc.com/D2128
llvm-svn: 194615
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Like GCC, this re-uses the 'f' constraint and a new 'w' print-modifier:
asm ("ldi.w %w0, 1", "=f"(result));
Unlike GCC, the 'w' print-modifer is not _required_ to produce the intended
output. This is a consequence of differences in the internal handling of
the registers in each compiler. To be source-compatible between the
compilers, users must use the 'w' print-modifier.
MSA registers (including control registers) are supported in clobber lists.
llvm-svn: 194476
|
| |
|
|
|
|
|
| |
Change SizeType, PtrDiffType, IntPtrType, WCharType, WIntType
to follow the XMOS llvm-gcc front end's settings.
llvm-svn: 194461
|
| |
|
|
| |
llvm-svn: 194446
|
| |
|
|
|
|
|
|
|
|
| |
substitution failure, allow a flag to be set on the Diagnostic object,
to mark it as 'causes substitution failure'.
Refactor Diagnostic.td and the tablegen to use an enum for SFINAE behavior
rather than a bunch of flags.
llvm-svn: 194444
|
| |
|
|
|
|
| |
the floating point register mode.
llvm-svn: 194426
|
| |
|
|
| |
llvm-svn: 194408
|
| |
|
|
|
|
|
| |
__FLT_EVAL_METHOD__ accordingly. Add test case for this and the SSE2
variances on NetBSD.
llvm-svn: 194377
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change fixes Richard's testcase for r193815. Now we include non-explicit
submodules into the list of exports.
The test failed previously because:
- recursive_visibility_a1.inner is not imported (only recursive_visibility_a1 is),
- thus the 'inner' submodule is not showing up in any of the import lists,
- and because of this getExportedModules() is not returning the
correct module set -- it only considers modules that are imported.
The fix is to make Module::getExportedModules() include non-explicit submodules
into the list of exports.
llvm-svn: 194018
|
| |
|
|
| |
llvm-svn: 193985
|
| |
|
|
| |
llvm-svn: 193850
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change makes Module::buildVisibleModulesCache() collect exported modules
recursively.
While computing a set of exports, getExportedModules() iterates over the set of
imported modules and filters it. But it does not consider the set of exports
of those modules -- it is the responsibility of the caller to do this.
Here is a certain instance of this issue. Module::isModuleVisible says that
CoreFoundation.CFArray submodule is not visible from Cocoa. Why?
- Cocoa imports Foundation.
- Foundation has an export restriction: "export *".
- Foundation imports CoreFoundation. (Just the top-level module.)
- CoreFoundation exports CoreFoundation.CFArray.
To decide which modules are visible from Cocoa, we collect all exported modules
from immediate imports in Cocoa:
> visibleModulesFro(Cocoa) = exported(Foundation) + exported(CoreData) + exported(AppKit)
To find out which modules are exported, we filter imports according to
restrictions:
> exported(Foundation) = filterByModuleMapRestrictions(imports(Foundation))
Because Foundation imports CoreFoundation (not CoreFoundation.CFArray), the
CFArray submodule is considered not exported from Foundation, and is not
visible from Cocoa (according to Module::isModuleVisible).
llvm-svn: 193815
|