search for: readerarch

...do you think we should continue using llvm/lib/ArchiveReader ? > > I was chatting with Michael and looks like there have been discussions and small sketches done on reading archive libraries in lld. Can you provide pointers to the design ? The general idea is to have a new Reader class (i.e. ReaderArchive) along with a ReaderOptionsArchive class. One of the options will be if all members are force loaded or not. The ReaderArchive ::parseFile() method will check the force-load option, if true it will parse up all the members and return an vector<> of File* objects, one for each member....

Hi Nick, Here is my understanding, 1) lld-core creates a ReaderOptionsArchive class with the (Reader, CommandLine options flag) 2) lld-core creates an object of type ReaderArchive(ReaderOptions), that users would subclass (off ArchiveLibraryFile) a) GNUArchiveLibrary b) BSDArchiveLibrary b) MachOArchiveLibrary c) COFFArchiveLibrary 3) ReaderArchive has two functions a) parseFile that returns a vector of file objects, if the force load option is...

Hi, I have started to work on support for Reading archive libraries in lld and thought of using the llvm/lib/ArchiveReader for this. The ArchiveReader doesnot fully support GNU archive libraries (thin archives), do you think we should continue using llvm/lib/ArchiveReader ? I was chatting with Michael and looks like there have been discussions and small sketches done on reading archive

On Oct 23, 2012, at 1:01 PM, Shankar Easwaran wrote: > Hi Nick, > > Here is my understanding, > > 1) lld-core creates a ReaderOptionsArchive class with the (Reader, CommandLine options flag) > 2) lld-core creates an object of type ReaderArchive(ReaderOptions), that users would subclass (off ArchiveLibraryFile) > a) GNUArchiveLibrary > b) BSDArchiveLibrary > b) MachOArchiveLibrary > c) COFFArchiveLibrary > 3) ReaderArchive has two functions > a) parseFile that returns a vector of file objects, if t...