search for: resolveropt

...providing class to make command line parsing easy. > 2) lld/Core providing utilities for managing search paths (for finding input files). > 3) Each platform has its own main() which: > 3a) uses the generic command line utilities to parse the options > 3b) uses the options to set up the ResolverOptions > 3c) calls Core/Resolver > 3d) calls appropriate Passes (may depend on command line options) > 3e) calls its platform executable writer, using private interface to specify platform specific options > > > Thoughts? > > -Nick The problem I see with this is embeddability...

...to make command line parsing easy. >> 2) lld/Core providing utilities for managing search paths (for finding input files). >> 3) Each platform has its own main() which: >> 3a) uses the generic command line utilities to parse the options >> 3b) uses the options to set up the ResolverOptions >> 3c) calls Core/Resolver >> 3d) calls appropriate Passes (may depend on command line options) >> 3e) calls its platform executable writer, using private interface to specify platform specific options >> >> >> Thoughts? >> >> -Nick > >...

...line parsing easy. >>> 2) lld/Core providing utilities for managing search paths (for finding input files). >>> 3) Each platform has its own main() which: >>> 3a) uses the generic command line utilities to parse the options >>> 3b) uses the options to set up the ResolverOptions >>> 3c) calls Core/Resolver >>> 3d) calls appropriate Passes (may depend on command line options) >>> 3e) calls its platform executable writer, using private interface to specify platform specific options >>> >>> >>> Thoughts? >>>...

...rce load) > > There are os/architecture specific portions of resolving symbols with the archive libraries when it comes to common symbols, do you have any suggestions on this ? There may need to be some ReaderOptionsArchive flags for how commons should be handled. There should also be some ResolverOptions for how commons are handled. I don't know how much the archive file format varies across platforms. In particular the table-of-contents file may be named differently and have a different format. Again we may need ReaderOptionsArchive flags to drive this, or maybe the ReaderOptionsArchi...

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

...gt;> >> There are os/architecture specific portions of resolving symbols with the archive libraries when it comes to common symbols, do you have any suggestions on this ? > There may need to be some ReaderOptionsArchive flags for how commons should be handled. There should also be some ResolverOptions for how commons are handled. > > I don't know how much the archive file format varies across platforms. In particular the table-of-contents file may be named differently and have a different format. Again we may need ReaderOptionsArchive flags to drive this, or maybe the ReaderOptio...

...>>> There are os/architecture specific portions of resolving symbols with the archive libraries when it comes to common symbols, do you have any suggestions on this ? >> There may need to be some ReaderOptionsArchive flags for how commons should be handled. There should also be some ResolverOptions for how commons are handled. >> >> I don't know how much the archive file format varies across platforms. In particular the table-of-contents file may be named differently and have a different format. Again we may need ReaderOptionsArchive flags to drive this, or maybe the...