| #
6dbbab68 |
| 09-Sep-2010 |
Dan Gohman <[email protected]> |
Discard metadata produced by LLVM 2.7. The value enumeration it used is different from what the code now uses in a two ways: NamedMDNodes were considered Values and included in the numbering, and the
Discard metadata produced by LLVM 2.7. The value enumeration it used is different from what the code now uses in a two ways: NamedMDNodes were considered Values and included in the numbering, and the function-local metadata counter wasn't reset between functions.
The later problem breaks lazy deserialization, so instead of trying to emulate the old numbering, just drop the old metadata. The only in-tree use case is debug info with LTO, where the QOI loss is considered acceptable.
llvm-svn: 113557
show more ...
|
|
Revision tags: llvmorg-2.8.0-rc1 |
|
| #
65b48b5d |
| 04-Sep-2010 |
Chris Lattner <[email protected]> |
zap dead code.
llvm-svn: 113073
|
|
Revision tags: llvmorg-2.8.0-rc0 |
|
| #
13ee795c |
| 28-Aug-2010 |
Chris Lattner <[email protected]> |
remove unions from LLVM IR. They are severely buggy and not being actively maintained, improved, or extended.
llvm-svn: 112356
|
| #
9b9ff467 |
| 25-Aug-2010 |
Dan Gohman <[email protected]> |
Add a FIXME comment.
llvm-svn: 112083
|
| #
26d837d0 |
| 25-Aug-2010 |
Dan Gohman <[email protected]> |
Fix the bitcode reader to clear out function-specific state from MDValueList between each function, now that the bitcode writer is reusing the index space for function-local metadata.
llvm-svn: 1120
Fix the bitcode reader to clear out function-specific state from MDValueList between each function, now that the bitcode writer is reusing the index space for function-local metadata.
llvm-svn: 112082
show more ...
|
| #
950ad658 |
| 25-Aug-2010 |
Dan Gohman <[email protected]> |
Fix a bug found by inspection.
llvm-svn: 112081
|
| #
4a68f9b6 |
| 25-Aug-2010 |
Dan Gohman <[email protected]> |
Add a comment.
llvm-svn: 112080
|
| #
578ee407 |
| 20-Aug-2010 |
Bill Wendling <[email protected]> |
Create the new linker type "linker_private_weak_def_auto".
It's similar to "linker_private_weak", but it's known that the address of the object is not taken. For instance, functions that had an inli
Create the new linker type "linker_private_weak_def_auto".
It's similar to "linker_private_weak", but it's known that the address of the object is not taken. For instance, functions that had an inline definition, but the compiler decided not to inline it. Note, unlike linker_private and linker_private_weak, linker_private_weak_def_auto may have only default visibility. The symbols are removed by the linker from the final linked image (executable or dynamic library).
llvm-svn: 111684
show more ...
|
| #
16a5d98c |
| 20-Aug-2010 |
Dan Gohman <[email protected]> |
Introduce a new temporary MDNode concept. Temporary MDNodes are not part of the IR, are not uniqued, and may be safely RAUW'd. This replaces a variety of alternate mechanisms for achieving the same e
Introduce a new temporary MDNode concept. Temporary MDNodes are not part of the IR, are not uniqued, and may be safely RAUW'd. This replaces a variety of alternate mechanisms for achieving the same effect.
llvm-svn: 111681
show more ...
|
| #
d0fcc9a8 |
| 15-Aug-2010 |
Argyrios Kyrtzidis <[email protected]> |
Revert r111082. No warnings for this common pattern.
llvm-svn: 111102
|
| #
7c09ddf0 |
| 14-Aug-2010 |
Argyrios Kyrtzidis <[email protected]> |
Add ATTRIBUTE_UNUSED to methods that are not supposed to be used.
llvm-svn: 111082
|
| #
2637cc1a |
| 21-Jul-2010 |
Dan Gohman <[email protected]> |
Make NamedMDNode not be a subclass of Value, and simplify the interface for creating and populating NamedMDNodes.
llvm-svn: 109061
|
| #
093cb79d |
| 21-Jul-2010 |
Dan Gohman <[email protected]> |
Disallow null as a named metadata operand. Make MDNode::destroy private. Fix the one thing that used MDNode::destroy, outside of MDNode itself.
One should never delete or destroy an MDNode explicitl
Disallow null as a named metadata operand. Make MDNode::destroy private. Fix the one thing that used MDNode::destroy, outside of MDNode itself.
One should never delete or destroy an MDNode explicitly. MDNodes implicitly go away when there are no references to them (implementation details aside).
llvm-svn: 109028
show more ...
|
| #
43aa8f03 |
| 20-Jul-2010 |
Dan Gohman <[email protected]> |
Add support for remapping metadata kind IDs when reading in a bitcode file, so that two bitcode files where the same metadata kind name happens to have been assigned a different ID can still be linke
Add support for remapping metadata kind IDs when reading in a bitcode file, so that two bitcode files where the same metadata kind name happens to have been assigned a different ID can still be linked together.
Eliminate the restriction that metadata kind IDs can't be 0.
Change MD_dbg from 1 to 0, because we can now, and because it's less mysterious that way.
llvm-svn: 108939
show more ...
|
| #
1e0213a7 |
| 13-Jul-2010 |
Dan Gohman <[email protected]> |
Add support for empty metadata nodes: !{}.
llvm-svn: 108259
|
| #
2c0ab48a |
| 09-Jul-2010 |
Gabor Greif <[email protected]> |
cache result of operator*
llvm-svn: 107979
|
| #
03bcd6ec |
| 01-Jul-2010 |
Bill Wendling <[email protected]> |
Implement the "linker_private_weak" linkage type. This will be used for Objective-C metadata types which should be marked as "weak", but which the linker will remove upon final linkage. However, this
Implement the "linker_private_weak" linkage type. This will be used for Objective-C metadata types which should be marked as "weak", but which the linker will remove upon final linkage. However, this linkage isn't specific to Objective-C.
For example, the "objc_msgSend_fixup_alloc" symbol is defined like this:
.globl l_objc_msgSend_fixup_alloc .weak_definition l_objc_msgSend_fixup_alloc .section __DATA, __objc_msgrefs, coalesced .align 3 l_objc_msgSend_fixup_alloc: .quad _objc_msgSend_fixup .quad L_OBJC_METH_VAR_NAME_1
This is different from the "linker_private" linkage type, because it can't have the metadata defined with ".weak_definition".
Currently only supported on Darwin platforms.
llvm-svn: 107433
show more ...
|
| #
36321717 |
| 29-Jun-2010 |
Bill Wendling <[email protected]> |
Revert r107205 and r107207.
llvm-svn: 107215
|
| #
1767723d |
| 29-Jun-2010 |
Bill Wendling <[email protected]> |
Introducing the "linker_weak" linkage type. This will be used for Objective-C metadata types which should be marked as "weak", but which the linker will remove upon final linkage. For example, the "o
Introducing the "linker_weak" linkage type. This will be used for Objective-C metadata types which should be marked as "weak", but which the linker will remove upon final linkage. For example, the "objc_msgSend_fixup_alloc" symbol is defined like this:
.globl l_objc_msgSend_fixup_alloc .weak_definition l_objc_msgSend_fixup_alloc .section __DATA, __objc_msgrefs, coalesced .align 3 l_objc_msgSend_fixup_alloc: .quad _objc_msgSend_fixup .quad L_OBJC_METH_VAR_NAME_1
This is different from the "linker_private" linkage type, because it can't have the metadata defined with ".weak_definition".
llvm-svn: 107205
show more ...
|
| #
9da5bb07 |
| 28-May-2010 |
Dan Gohman <[email protected]> |
Bitcode support for allocas with arbitrary array size types.
llvm-svn: 104915
|
|
Revision tags: llvmorg-2.7.0 |
|
| #
07d09ed4 |
| 03-Apr-2010 |
Chris Lattner <[email protected]> |
Add special case bitcode support for DebugLoc. This avoids having the bitcode writer materialize mdnodes for all the debug location tuples when writing out the bc file and stores the information in
Add special case bitcode support for DebugLoc. This avoids having the bitcode writer materialize mdnodes for all the debug location tuples when writing out the bc file and stores the information in a more compact form. For example, the -O0 -g bc file for combine.c in 176.gcc shrinks from 739392 to 512096 bytes.
This concludes my planned short-term debug info work.
llvm-svn: 100261
show more ...
|
| #
e447aeb9 |
| 02-Apr-2010 |
Dan Gohman <[email protected]> |
If the bitcode reader input stream isn't a multiple of 4 bytes, it's more likely not a bitcode file at all, rather than being a bitcode file which is truncated. Check for this case and issue a more r
If the bitcode reader input stream isn't a multiple of 4 bytes, it's more likely not a bitcode file at all, rather than being a bitcode file which is truncated. Check for this case and issue a more relevant error message.
llvm-svn: 100156
show more ...
|
| #
8fce3ddd |
| 16-Mar-2010 |
Chris Lattner <[email protected]> |
reapply r98656 unmodified, which exposed the asmprinter not handling constant unions.
llvm-svn: 98680
|
| #
3a374da9 |
| 16-Mar-2010 |
Daniel Dunbar <[email protected]> |
Revert r98656, its breaking all over the place.
llvm-svn: 98662
|
| #
9ae99e0d |
| 16-Mar-2010 |
Chris Lattner <[email protected]> |
improve support for uniontype and ConstantUnion, patch by Tim Northover!
llvm-svn: 98656
|