search for: objtxt

Hi, We have a whole bunch of readers(we would have some more too), and was thinking if we should have a vector of Readers, and have a function isMyFormat in each of them. Any reader that knows to handle, goes ahead and parses the file. On a side note, we currently use .objtxt as an figure out if the file is a YAML file or not. I have added FIXME's in the code, if we could some kind of magic (or) a better way to figure out if the file is YAML ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foun...

...have a whole bunch of readers(we would have some more too), and was thinking if we should have a vector of Readers, and have a function isMyFormat in each of them. >> >> Any reader that knows to handle, goes ahead and parses the file. >> >> On a side note, we currently use .objtxt as an figure out if the file is a YAML file or not. I have added FIXME's in the code, if we could some kind of magic (or) a better way to figure out if the file is YAML ? > On this topic, we should come up with standard file extension names. I made up .objtxt for atoms-in-yaml when writing...

...wrote: > We have a whole bunch of readers(we would have some more too), and was thinking if we should have a vector of Readers, and have a function isMyFormat in each of them. > > Any reader that knows to handle, goes ahead and parses the file. > > On a side note, we currently use .objtxt as an figure out if the file is a YAML file or not. I have added FIXME's in the code, if we could some kind of magic (or) a better way to figure out if the file is YAML ? On this topic, we should come up with standard file extension names. I made up .objtxt for atoms-in-yaml when writing the...

...as >>>> thinking if we should have a vector of Readers, and have a function >>>> isMyFormat in each of them. >>>> >>>> Any reader that knows to handle, goes ahead and parses the file. >>>> >>>> On a side note, we currently use .objtxt as an figure out if the file >>>> is a YAML file or not. I have added FIXME's in the code, if we could some >>>> kind of magic (or) a better way to figure out if the file is YAML ? >>>> >>> On this topic, we should come up with standard file extensio...

...some more too), and >>> was thinking if we should have a vector of Readers, and have a >>> function isMyFormat in each of them. >>> >>> Any reader that knows to handle, goes ahead and parses the file. >>> >>> On a side note, we currently use .objtxt as an figure out if the >>> file is a YAML file or not. I have added FIXME's in the code, if we >>> could some kind of magic (or) a better way to figure out if the file >>> is YAML ? >> On this topic, we should come up with standard file extension names. &g...

...inning of a file. A magic string which is valid as a YAML, such as "magic:" is IMO less flexible and should be avoided. > PS: This has been snipped from an earlier discussion with Tim. > > (b) > > lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o > atoms.objtxt (Create a atom file using x86_64 target) > lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) > > You can create yaml files from each flavor and pass it to the wrong > flavor, too. > > If we have the magic and arch in the yaml file (or) one entry combined > trip...

...86_64 --output-filetype=yaml -r - | lld -flavor gnu -target x86_64 - Which is certainly not doable because you dont have a file created on the filesystem. PS: This has been snipped from an earlier discussion with Tim. (b) lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o atoms.objtxt (Create a atom file using x86_64 target) lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) You can create yaml files from each flavor and pass it to the wrong flavor, too. If we have the magic and arch in the yaml file (or) one entry combined triple(that combines flavor, operat...

...llows key-value pairs. #!obj are all invalid characters for > YAML files. > > >> PS: This has been snipped from an earlier discussion with Tim. >>> >>> (b) >>> >>> lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o >>> atoms.objtxt (Create a atom file using x86_64 target) >>> lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) >>> >>> You can create yaml files from each flavor and pass it to the wrong >>> flavor, too. >>> >>> If we have the magic and arch in...

...should be avoided. YAML only allows key-value pairs. #!obj are all invalid characters for YAML files. > >> PS: This has been snipped from an earlier discussion with Tim. >> >> (b) >> >> lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o >> atoms.objtxt (Create a atom file using x86_64 target) >> lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) >> >> You can create yaml files from each flavor and pass it to the wrong >> flavor, too. >> >> If we have the magic and arch in the yaml file (or) one...

...s. #!obj are all invalid characters for >> YAML files. >> >> >>> PS: This has been snipped from an earlier discussion with Tim. >>>> (b) >>>> >>>> lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o >>>> atoms.objtxt (Create a atom file using x86_64 target) >>>> lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) >>>> >>>> You can create yaml files from each flavor and pass it to the wrong >>>> flavor, too. >>>> >>>> If we ha...

...t;> YAML files. >>> >>> >>> PS: This has been snipped from an earlier discussion with Tim. >>>> >>>>> (b) >>>>> >>>>> lld -flavor gnu -target x86_64 input.o --output-filetype=yaml -o >>>>> atoms.objtxt (Create a atom file using x86_64 target) >>>>> lld -flavor gnu -target hexagon atoms.objtxt (use it with hexagon) >>>>> >>>>> You can create yaml files from each flavor and pass it to the wrong >>>>> flavor, too. >>>>> >&...

...h of readers(we would have some more too), and was >> thinking if we should have a vector of Readers, and have a function >> isMyFormat in each of them. >> >> Any reader that knows to handle, goes ahead and parses the file. >> >> On a side note, we currently use .objtxt as an figure out if the file is >> a YAML file or not. I have added FIXME's in the code, if we could some kind >> of magic (or) a better way to figure out if the file is YAML ? >> >> Thanks >> >> Shankar Easwaran >> >> -- >> Qualcomm Innovat...

...ve some more too), and was >>> thinking if we should have a vector of Readers, and have a function >>> isMyFormat in each of them. >>> >>> Any reader that knows to handle, goes ahead and parses the file. >>> >>> On a side note, we currently use .objtxt as an figure out if the file is >>> a YAML file or not. I have added FIXME's in the code, if we could some kind >>> of magic (or) a better way to figure out if the file is YAML ? >>> >>> Thanks >>> >>> Shankar Easwaran >>> >>&...

...gt; We have a whole bunch of readers(we would have some more too), and was > thinking if we should have a vector of Readers, and have a function > isMyFormat in each of them. > > Any reader that knows to handle, goes ahead and parses the file. > > On a side note, we currently use .objtxt as an figure out if the file is a > YAML file or not. I have added FIXME's in the code, if we could some kind > of magic (or) a better way to figure out if the file is YAML ? > > Thanks > > Shankar Easwaran > > -- > Qualcomm Innovation Center, Inc. is a member of Code...

...gt; We have a whole bunch of readers(we would have some more too), and was > thinking if we should have a vector of Readers, and have a function > isMyFormat in each of them. > > Any reader that knows to handle, goes ahead and parses the file. > > On a side note, we currently use .objtxt as an figure out if the file is a > YAML file or not. I have added FIXME's in the code, if we could some kind > of magic (or) a better way to figure out if the file is YAML ? > > Thanks > > Shankar Easwaran > > -- > Qualcomm Innovation Center, Inc. is a member of Code...

...h of readers(we would have some more too), and was >> thinking if we should have a vector of Readers, and have a function >> isMyFormat in each of them. >> >> Any reader that knows to handle, goes ahead and parses the file. >> >> On a side note, we currently use .objtxt as an figure out if the file is a >> YAML file or not. I have added FIXME's in the code, if we could some kind >> of magic (or) a better way to figure out if the file is YAML ? >> >> Thanks >> >> Shankar Easwaran >> >> -- >> Qualcomm Innovat...

...as >>>> thinking if we should have a vector of Readers, and have a function >>>> isMyFormat in each of them. >>>> >>>> Any reader that knows to handle, goes ahead and parses the file. >>>> >>>> On a side note, we currently use .objtxt as an figure out if the file is >>>> a YAML file or not. I have added FIXME's in the code, if we could some >>>> kind >>>> of magic (or) a better way to figure out if the file is YAML ? >>>> >>>> Thanks >>>> >>>&gt...

...codeaurora.org> wrote: Hi, We have a whole bunch of readers(we would have some more too), and was thinking if we should have a vector of Readers, and have a function isMyFormat in each of them. Any reader that knows to handle, goes ahead and parses the file. On a side note, we currently use .objtxt as an figure out if the file is a YAML file or not. I have added FIXME's in the code, if we could some kind of magic (or) a better way to figure out if the file is YAML ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundat...

...thinking if we should have a vector of Readers, and have a function >>>>> isMyFormat in each of them. >>>>> >>>>> Any reader that knows to handle, goes ahead and parses the file. >>>>> >>>>> On a side note, we currently use .objtxt as an figure out if the file >>>>> is >>>>> a YAML file or not. I have added FIXME's in the code, if we could some >>>>> kind >>>>> of magic (or) a better way to figure out if the file is YAML ? >>>>> >>>>&gt...

...ber of parallel lit tests changes which tests fail (for example, running a second time adds tests under COFF). And, FWIW, these tests generally fail on my system (for reasons seemingly unrelated to the thread/process resource issue): lld :: Driver/lib-search.test lld :: Driver/undef-basic.objtxt lld :: elf2/dynamic-reloc.s lld :: elf2/shared.s lld :: elf2/soname.s lld :: elf/librarynotfound.test lld :: elf/responsefile.test lld :: mach-o/dylib-install-names.yaml lld :: mach-o/force_load-dylib.yaml lld :: mach-o/lib-search-paths.yaml lld :: mach-o/parse-t...