| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
field to memcpy, memmove, and memset.
llvm-svn: 100305
|
| |
|
|
| |
llvm-svn: 100236
|
| |
|
|
| |
llvm-svn: 100235
|
| |
|
|
| |
llvm-svn: 100200
|
| |
|
|
|
|
| |
field to memcpy, memmove, and memset.
llvm-svn: 100193
|
| |
|
|
|
|
| |
instruction.
llvm-svn: 99962
|
| |
|
|
| |
llvm-svn: 99960
|
| |
|
|
| |
llvm-svn: 99949
|
| |
|
|
|
|
| |
Fixes PR3782.
llvm-svn: 99940
|
| |
|
|
|
|
|
|
| |
double 0.000000e+000
instead of
double 0.000000e+00
llvm-svn: 99932
|
| |
|
|
|
|
| |
memmove, and memset
llvm-svn: 99930
|
| |
|
|
|
|
|
|
| |
This introduces FunctionType::ExtInfo to hold the calling convention and the
noreturn attribute. The next patch will extend it to include the regparm
attribute and fix the bug.
llvm-svn: 99920
|
| |
|
|
|
|
|
| |
instead of the canonical parameter type (which has correctly dropped all such
direct qualifiers). Fixes PR6695.
llvm-svn: 99688
|
| |
|
|
| |
llvm-svn: 99616
|
| |
|
|
|
|
|
| |
gcc, and the common expectation seems to be that they are unused. If and when
someone cares we can add them back with well documented demantics.
llvm-svn: 99522
|
| |
|
|
|
|
|
|
| |
semantics.
- This should be conservatively correct, we eventually should have target hooks for platforms that are less strict.
llvm-svn: 99050
|
| |
|
|
|
|
|
|
| |
expression computation in the wrong bit-width, and end up generating a totally
bogus array reference (_g0+8589934546).
- This showed up on Prolangs/cdecl.
llvm-svn: 99042
|
| |
|
|
| |
llvm-svn: 98264
|
| |
|
|
|
|
| |
strict verifier that ignores debug info for such types if their file info is unknown.
llvm-svn: 98096
|
| |
|
|
|
|
| |
code in PR6537. This should be reverted when the ast bug is fixed.
llvm-svn: 97981
|
| |
|
|
|
|
|
| |
I'm reasonably sure my implementation is correct, but it would be nice if
someone could double-check.
llvm-svn: 97864
|
| |
|
|
|
|
| |
test case.
llvm-svn: 97777
|
| |
|
|
|
|
| |
alternate struct return ABI
llvm-svn: 97775
|
| |
|
|
| |
llvm-svn: 97750
|
| |
|
|
|
|
|
|
|
| |
Clang's support for weakref is now better than llvm-gcc's :-)
We don't introduce a new symbol and we correctly mark undefined references weak only if there is no
definition or regular undefined references in the same file.
llvm-svn: 97733
|
| |
|
|
|
|
| |
Our testing framework can't deal with disabled targets yet.
llvm-svn: 97719
|
| |
|
|
|
|
| |
targets except X86.
llvm-svn: 97718
|
| |
|
|
|
|
| |
Re-enable test.
llvm-svn: 97707
|
| |
|
|
| |
llvm-svn: 97700
|
| |
|
|
|
|
| |
'%t' file was left around on my disk. doh.
llvm-svn: 97699
|
| |
|
|
|
|
| |
XFAIL and already tracked in bugzilla.
llvm-svn: 97671
|
| |
|
|
| |
llvm-svn: 97669
|
| |
|
|
| |
llvm-svn: 97656
|
| |
|
|
|
|
|
|
| |
evaluation of __builtin_nan*. Most of the work to make this work is in LLVM.
Fixes <rdar://problem/7696712> and part of PR 5255.
llvm-svn: 97383
|
| |
|
|
| |
llvm-svn: 97035
|
| |
|
|
| |
llvm-svn: 97032
|
| |
|
|
|
|
|
|
|
|
|
| |
a common source of oddities and, in theory, removes some redundant ABI
computations. Also fixes a miscompile I introduced yesterday by refactoring
some code and causing a slightly different code path to be taken that
didn't perform *parameter* type canonicalization, just normal type
canonicalization; this in turn caused a bit of ABI code to misfire because
it was looking for 'double' or 'float' but received 'const float'.
llvm-svn: 97030
|
| |
|
|
| |
llvm-svn: 96999
|
| |
|
|
|
|
| |
temporary name
llvm-svn: 96998
|
| |
|
|
|
|
| |
llvm-gcc does, but are more strict on what uses of weakref we accept.
llvm-svn: 96992
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the block descriptor field. This field is the ObjC style @encode
signature of the implementation function, and was to this point
conditionally provided in the block literal data structure. That
provisional support is removed.
Additionally, eliminate unused enumerations for the block literal flags field.
The first shipping ABI unconditionally set (1<<29) but this bit is unused
by the runtime, so the second ABI will unconditionally have (1<<30) set so
that the runtime can in fact distinguish whether the additional data is
present or not.
llvm-svn: 96989
|
| |
|
|
| |
llvm-svn: 96958
|
| |
|
|
|
|
| |
does. Fixes PR5253.
llvm-svn: 96553
|
| |
|
|
| |
llvm-svn: 96397
|
| |
|
|
|
|
|
|
| |
Win32-specific.
Also, fix a test to use FileCheck instead of grepping LLVM IR.
llvm-svn: 96364
|
| |
|
|
|
|
| |
objc method. :)
llvm-svn: 96245
|
| |
|
|
|
|
|
| |
marked 'force_align_arg_pointer'. Almost there; now all I need to do is finish
up the backend.
llvm-svn: 96100
|
| |
|
|
|
|
| |
self, _cmd etc.
llvm-svn: 95743
|
| |
|
|
|
|
|
|
|
|
| |
particular type, and flood fill. - CreateMemTemp sets the alignment on the alloca correctly, which fixes a great many places in IRgen where we were doing the wrong thing.
- This fixes many many more places than the test case, but my feeling is we need to audit alignment systematically so I'm not inclined to try hard to test the individual fixes in this patch. If this bothers you, patches welcome!
PR6240.
llvm-svn: 95648
|
| |
|
|
|
|
|
|
|
|
|
|
| |
follows (as conservatively as possible) gcc's current behavior: attributes
written on return types that don't apply there are applied to the function
instead, etc. Only parse CC attributes as type attributes, not as decl attributes;
don't accepet noreturn as a decl attribute on ValueDecls, either (it still
needs to apply to other decls, like blocks). Consistently consume CC/noreturn
information throughout codegen; enforce this by removing their default values
in CodeGenTypes::getFunctionInfo().
llvm-svn: 95436
|