search for: inputel

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 p...

...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...

...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...

...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 wi...

...nd create a group node, and add it after the command line is processed to the inputGraph. PS : Does Darwin have a command line option to handle files in the order specified in the command line for libraries ? If so, then the above would break I am planning to support other operations too like inputElement->setPosition(InputGraph::Top) inputElement->setPosition(InputGraph::Last) inputElement->setPosition(InputGraph::Position, <value>) The user has to explicitly call a seperate api so that the elements are ordered according to whatever the user wants. inputGraph->insertInputE...

...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...

...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. >> >...

...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 t...

...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 Li...

...-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 >>&gt...

...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. > > > &g...

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