Displaying 3 results from an estimated 3 matches for "bitstreamentri".
Did you mean:
bitstreamentry
2020 Aug 28
2
End-to-end -fembed-bitcode .llvmbc and .llvmcmd
Hi Mircea,
If you use an ordinary linker that concatenates .llvmbc sections, you can use this code to get the size of each bitcode module. As far as I know, there's no clean way to separate the .llvmcmd sections without making assumptions about what options were used.
// Given a bitcode file followed by garbage, get the size of the actual
// bitcode. This only works correctly with some kinds
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>>
>> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>>
2020 Aug 28
4
End-to-end -fembed-bitcode .llvmbc and .llvmcmd
You should probably pull in some folks who implemented/maintain the feature
for Darwin.
I guess they aren't linking this info, but only communicating in the object
file between tools - maybe they flag these sections (either in the object,
or by the linker) as ignored/dropped during linking. That semantic could be
implemented in ELF too by marking the sections SHF_IGNORED or something