search for: inputelements

Hi Nick, These are the below modifications needed in lld to start processing groups :- 1) LinkerInput would be moved to FileNode that contains the following functions - getBuffer - takeBuffer - getPath 2) The driver will process the vector of InputElements and call /*process */on each of them. process() would create a lld::File object within the InputElement if its a FileNode process() would create a vector of lld::File objects within the InputElement if its a ControlNode 3) The resolver will not process each file but it would process...

...k, > > These are the below modifications needed in lld to start processing groups :- > > 1) LinkerInput would be moved to FileNode that contains the following functions > - getBuffer > - takeBuffer > - getPath > > 2) The driver will process the vector of InputElements and call process on each of them. > process() would create a lld::File object within the InputElement if its a FileNode > process() would create a vector of lld::File objects within the InputElement if its a ControlNode > > 3) The resolver will not process each file but it wo...

...lution is possible). Thanks Shankar Easwaran > > -Nick > > On Sep 4, 2013, at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > >> Hi, >> >> With the inputGraph now, lld models command line options, input files as nodes in the InputGraph called InputElements. >> >> In the current approach, each InputElement is converted to a LinkerInput, which works if all lld deals with individual files. >> >> Dealing with ControlNodes (Groups), have a problem with it, on how to model that as a LinkerInput. >> >> Joerg/Me were chatt...

...ulfilled, then move on in the graph. -Nick >> On Sep 4, 2013, at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: >> >>> Hi, >>> >>> With the inputGraph now, lld models command line options, input files as nodes in the InputGraph called InputElements. >>> >>> In the current approach, each InputElement is converted to a LinkerInput, which works if all lld deals with individual files. >>> >>> Dealing with ControlNodes (Groups), have a problem with it, on how to model that as a LinkerInput. >>> >&...

Hi, With the inputGraph now, lld models command line options, input files as nodes in the InputGraph called InputElements. In the current approach, each InputElement is converted to a LinkerInput, which works if all lld deals with individual files. Dealing with ControlNodes (Groups), have a problem with it, on how to model that as a LinkerInput. Joerg/Me were chatting on the IRC about this and we came up with the...

On 9/5/2013 1:40 PM, Nick Kledzik wrote: > The way darwin works with the current scheme is that the files are added to InputFiles in command line order, then forEachInitialAtom() walks the whole list but only operates on the non-library (i.e. object files) and searchLibraries() only operates on library files. > > If we have the Resolver walk the graph, then either: > 1) We need some

...ly. What should the interface be that the Resolver uses for handling groups? -Nick On Sep 4, 2013, at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Hi, > > With the inputGraph now, lld models command line options, input files as nodes in the InputGraph called InputElements. > > In the current approach, each InputElement is converted to a LinkerInput, which works if all lld deals with individual files. > > Dealing with ControlNodes (Groups), have a problem with it, on how to model that as a LinkerInput. > > Joerg/Me were chatting on the IRC about...

...foo.a --as-needed bar.a --no-as-needed --end-group > > On Wed, Sep 4, 2013 at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > >> Hi, >> >> With the inputGraph now, lld models command line options, input files as >> nodes in the InputGraph called InputElements. >> >> In the current approach, each InputElement is converted to a LinkerInput, >> which works if all lld deals with individual files. >> >> Dealing with ControlNodes (Groups), have a problem with it, on how to >> model that as a LinkerInput. >> >> J...

...up and File? --start-group foo.a --as-needed bar.a --no-as-needed --end-group On Wed, Sep 4, 2013 at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > Hi, > > With the inputGraph now, lld models command line options, input files as > nodes in the InputGraph called InputElements. > > In the current approach, each InputElement is converted to a LinkerInput, > which works if all lld deals with individual files. > > Dealing with ControlNodes (Groups), have a problem with it, on how to > model that as a LinkerInput. > > Joerg/Me were chatting on the IRC...

...d --end-group >> >> On Wed, Sep 4, 2013 at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org >> >**wrote: >> >> Hi, >>> >>> With the inputGraph now, lld models command line options, input files as >>> nodes in the InputGraph called InputElements. >>> >>> In the current approach, each InputElement is converted to a LinkerInput, >>> which works if all lld deals with individual files. >>> >>> Dealing with ControlNodes (Groups), have a problem with it, on how to >>> model that as a LinkerIn...

...-end-group >>> >>> On Wed, Sep 4, 2013 at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org >>>> **wrote: >>> Hi, >>>> With the inputGraph now, lld models command line options, input files as >>>> nodes in the InputGraph called InputElements. >>>> >>>> In the current approach, each InputElement is converted to a LinkerInput, >>>> which works if all lld deals with individual files. >>>> >>>> Dealing with ControlNodes (Groups), have a problem with it, on how to >>>>...

...esolver uses for handling groups? > > -Nick > > On Sep 4, 2013, at 1:42 PM, Shankar Easwaran <shankare at codeaurora.org> > wrote: > > > Hi, > > > > With the inputGraph now, lld models command line options, input files as > nodes in the InputGraph called InputElements. > > > > In the current approach, each InputElement is converted to a > LinkerInput, which works if all lld deals with individual files. > > > > Dealing with ControlNodes (Groups), have a problem with it, on how to > model that as a LinkerInput. > > > > Joe...

Hi all, I've been thinking about how best to represent MachO's LC_REEXPORT_DYLIB (used even by libSystem.dylib to provide its various sub-components[*]). It looks like this functionality would naturally fall into the InputGraph, in analogy with Groups and Archives. Unfortunately, it's rather more dynamic than the existing cases: we don't know the needed files before parsing the