diff options
author | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2015-04-24 22:04:41 +0000 |
---|---|---|
committer | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2015-04-24 22:04:41 +0000 |
commit | 3d4cd756b6044837542acac3483e4cca7bc55814 (patch) | |
tree | 318f59eeec88d71fd46a82c96974a8d92f395d59 /llvm/lib/Linker/LinkModules.cpp | |
parent | 327e9bd399f8c1846b1cb967b03cd9f1e54af1e7 (diff) | |
download | bcm5719-llvm-3d4cd756b6044837542acac3483e4cca7bc55814.tar.gz bcm5719-llvm-3d4cd756b6044837542acac3483e4cca7bc55814.zip |
IR: Add assembly/bitcode support for function metadata attachments
Add serialization support for function metadata attachments (added in
r235783). The syntax is:
define @foo() !attach !0 {
Metadata attachments are only allowed on functions with bodies. Since
they come before the `{`, they're not really part of the body; since
they require a body, they're not really part of the header. In
`LLParser` I gave them a separate function called from `ParseDefine()`,
`ParseOptionalFunctionMetadata()`.
In bitcode, I'm using the same `METADATA_ATTACHMENT` record used by
instructions. Instruction metadata attachments are included in a
special "attachment" block at the end of a `Function`. The attachment
records are laid out like this:
InstID (KindID MetadataID)+
Note that these records always have an odd number of fields. The new
code takes advantage of this to recognize function attachments (which
don't need an instruction ID):
(KindID MetadataID)+
This means we can use the same attachment block already used for
instructions.
This is part of PR23340.
llvm-svn: 235785
Diffstat (limited to 'llvm/lib/Linker/LinkModules.cpp')
0 files changed, 0 insertions, 0 deletions