| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which versions of an OS provide a certain facility. For example,
void foo()
__attribute__((availability(macosx,introduced=10.2,deprecated=10.4,obsoleted=10.6)));
says that the function "foo" was introduced in 10.2, deprecated in
10.4, and completely obsoleted in 10.6. This attribute ties in with
the deployment targets (e.g., -mmacosx-version-min=10.1 specifies that
we want to deploy back to Mac OS X 10.1). There are several concrete
behaviors that this attribute enables, as illustrated with the
function foo() above:
- If we choose a deployment target >= Mac OS X 10.4, uses of "foo"
will result in a deprecation warning, as if we had placed
attribute((deprecated)) on it (but with a better diagnostic)
- If we choose a deployment target >= Mac OS X 10.6, uses of "foo"
will result in an "unavailable" warning (in C)/error (in C++), as
if we had placed attribute((unavailable)) on it
- If we choose a deployment target prior to 10.2, foo() is
weak-imported (if it is a kind of entity that can be weak
imported), as if we had placed the weak_import attribute on it.
Naturally, there can be multiple availability attributes on a
declaration, for different platforms; only the current platform
matters when checking availability attributes.
The only platforms this attribute currently works for are "ios" and
"macosx", since we already have -mxxxx-version-min flags for them and we
have experience there with macro tricks translating down to the
deprecated/unavailable/weak_import attributes. The end goal is to open
this up to other platforms, and even extension to other "platforms"
that are really libraries (say, through a #pragma clang
define_system), but that hasn't yet been designed and we may want to
shake out more issues with this narrower problem first.
Addresses <rdar://problem/6690412>.
As a drive-by bug-fix, if an entity is both deprecated and
unavailable, we only emit the "unavailable" diagnostic.
llvm-svn: 128127
|
|
|
|
|
|
|
|
|
| |
add support for the OpenCL __private, __local, __constant and
__global address spaces, as well as the __read_only, _read_write and
__write_only image access specifiers. Patch originally by ARM;
language-specific address space support by myself.
llvm-svn: 127915
|
|
|
|
| |
llvm-svn: 125282
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the width and align of bool type on Darwin to be 32bits
while keeping it 8 everywhere else.
Change the definition of va_list to default to SV4 ABI one
and let darwin subtarget override this.
Both changes submitted by Nathan Whitehorn and reviewed
by Rafael Espindola.
llvm-svn: 122956
|
|
|
|
|
|
|
| |
16-bits in size. Implement this by splitting WChar into two enums, like we have
for char. This fixes a miscompmilation of XULRunner, PR8856.
llvm-svn: 122558
|
|
|
|
| |
llvm-svn: 122194
|
|
|
|
|
|
| |
constraint it's invalid. Fixes PR3905.
llvm-svn: 118146
|
|
|
|
|
|
| |
constraint. Fixes PR3904.
llvm-svn: 118145
|
|
|
|
| |
llvm-svn: 116699
|
|
|
|
| |
llvm-svn: 114490
|
|
|
|
|
|
| |
for Clang side of support.
llvm-svn: 114253
|
|
|
|
|
|
| |
Allow '<' and '>' as constraints for input or output.
llvm-svn: 113246
|
|
|
|
|
|
|
| |
it deserves its own enumerator. Obviously the implementations should
closely follow the Itanium ABI except in cases of divergence.
llvm-svn: 111749
|
|
|
|
| |
llvm-svn: 110870
|
|
|
|
| |
llvm-svn: 110764
|
|
|
|
|
|
| |
we have the full fix.
llvm-svn: 110706
|
|
|
|
|
|
|
|
| |
whether to use objc_msgSend_fpret; the choice is target dependent, not Obj-C ABI
dependent.
- <rdar://problem/8139758> arm objc _objc_msgSend_fpret bug
llvm-svn: 108379
|
|
|
|
|
|
| |
constraints, per pr7338.
llvm-svn: 108028
|
|
|
|
| |
llvm-svn: 105500
|
|
|
|
| |
llvm-svn: 104789
|
|
|
|
|
|
| |
variants. This fixes neon inline asm which my patch for PR6780 broke.
llvm-svn: 102181
|
|
|
|
| |
llvm-svn: 101370
|
|
|
|
| |
llvm-svn: 101369
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Used to determine whether the alignment of the type in a bit-field is
respected when laying out structures. The default is true, targets can
override this as needed.
- This is designed to correspond to the PCC_BITFIELD_TYPE_MATTERS macro in
gcc. The AST/Sema implementation only affects one line, unless I have
forgotten something. I'd appreciate further review.
- IRgen still needs to be updated to fully support this (which is effectively
PR5591).
llvm-svn: 101356
|
|
|
|
| |
llvm-svn: 94917
|
|
|
|
| |
llvm-svn: 91540
|
|
|
|
|
|
| |
Ken Dyck.
llvm-svn: 89520
|
|
|
|
|
|
|
| |
into TargetInfo, just derive this based on the underlying type.
This prevents them from getting out of synch, patch by Ken Dyck!
llvm-svn: 86976
|
|
|
|
| |
llvm-svn: 86395
|
|
|
|
| |
llvm-svn: 86183
|
|
|
|
| |
llvm-svn: 86177
|
|
|
|
| |
llvm-svn: 86167
|
|
|
|
| |
llvm-svn: 85076
|
|
|
|
|
|
| |
patch by Ken Dyck!
llvm-svn: 84746
|
|
|
|
| |
llvm-svn: 84740
|
|
|
|
|
|
| |
previously we only recognized it on inputs.
llvm-svn: 83939
|
|
|
|
| |
llvm-svn: 81346
|
|
|
|
|
|
| |
an incremental patch
llvm-svn: 75622
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that I'm guessing that *BSD and Solaris do the same thing as Linux
here, but it's quite possible I'm wrong; if the following testcase
gives an error on x86-64 with gcc for any of those operating systems, please
tell me:
#include <stdint.h>
int64_t x; long x;
llvm-svn: 74583
|
|
|
|
| |
llvm-svn: 72928
|
|
|
|
|
|
|
| |
This recognizes all the target-independent constant constraints
that have target-specific meanings.
llvm-svn: 71064
|
|
|
|
|
|
| |
flags.
llvm-svn: 70137
|
|
|
|
| |
llvm-svn: 70136
|
|
|
|
|
|
| |
instead of passing it around in addition to it.
llvm-svn: 70135
|
|
|
|
|
|
| |
the enum along with some other data.
llvm-svn: 70114
|
|
|
|
|
|
|
|
| |
Let me know if I messed up for some target. Note that for Windows, we
should be able to support it (MSVC supports "__declspec(thread)"), but
I'm pretty sure LLVM doesn't know how to generate the correct code.
llvm-svn: 69552
|
|
|
|
|
|
| |
constraints string. This will make it possible to support multi-character constraints. No functionality change (for now).
llvm-svn: 65696
|
|
|
|
|
|
|
|
|
|
| |
a target.
Make Preprocessor.cpp define a new __INTPTR_TYPE__ macro based on this.
On linux/32, set intptr_t to int, instead of long. This fixes PR3563.
llvm-svn: 64495
|
|
|
|
|
|
| |
predefines buffer initialization.
llvm-svn: 63919
|
|
|
|
|
|
| |
same constraint info as the output constraint. Fixes PR3417
llvm-svn: 63127
|