search for: 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 of garbage (in // particular, it will work if the bitcode file is followed by zeros, or if // it's fol...

...a > specialized reader, of course - basically, achieve what Sean described, but > "by design". > > For instance, each .o file could have a size, followed by the payload > (maybe include in the payload the name of the module, too; maybe compress > it, too). Same for the .llvmcmd case. > > On Thu, Aug 27, 2020 at 6:57 PM Sean Bartell <smbarte2 at illinois.edu> > wrote: > >> 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 k...