search for: yaml2coff

You probably don't want to go down the same route that clang goes through to write the object file. If you think yaml2coff is convoluted, the way clang does it will just give you a headache. There are multiple abstractions involved to account for different object file formats (ELF, COFF, MachO) and output formats (Assembly, binary file). At least with yaml2coff It's true that yaml2coff is using the COFFParser st...

...28 PM Leonardo Santagada <santagada at gmail.com> wrote: > On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> > wrote: > >> You probably don't want to go down the same route that clang goes through >> to write the object file. If you think yaml2coff is convoluted, the way >> clang does it will just give you a headache. There are multiple >> abstractions involved to account for different object file formats (ELF, >> COFF, MachO) and output formats (Assembly, binary file). At least with >> yaml2coff >> > > I...

On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> wrote: > You probably don't want to go down the same route that clang goes through > to write the object file. If you think yaml2coff is convoluted, the way > clang does it will just give you a headache. There are multiple > abstractions involved to account for different object file formats (ELF, > COFF, MachO) and output formats (Assembly, binary file). At least with > yaml2coff > I think your phrase got cut th...

...and global hashes it (proof of concept kind of code). What I can't find is: how does clang itself writes the coff files with global hashes, as that might help me understand how to create the .debug$H section, how to update the file section count and how to properly write this back. The code on yaml2coff is expecting to be working on the yaml COFFParser struct and I'm having quite a bit of a headache turning the COFFObjectFile into a COFFParser object or compatible... Tomorrow I might try the very non efficient path of coff2yaml and then yaml2coff with the hashes header... but it seems way too...

...santagada at gmail.com> > wrote: > >> On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> >> wrote: >> >>> You probably don't want to go down the same route that clang goes >>> through to write the object file. If you think yaml2coff is convoluted, >>> the way clang does it will just give you a headache. There are multiple >>> abstractions involved to account for different object file formats (ELF, >>> COFF, MachO) and output formats (Assembly, binary file). At least with >>> yaml2coff >...

...gt;> wrote: >> >>> On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> >>> wrote: >>> >>>> You probably don't want to go down the same route that clang goes >>>> through to write the object file. If you think yaml2coff is convoluted, >>>> the way clang does it will just give you a headache. There are multiple >>>> abstractions involved to account for different object file formats (ELF, >>>> COFF, MachO) and output formats (Assembly, binary file). At least with >>>&gt...

...e hash values). Then when you're writing the list of sections, just add in the .debug$H section right after the .debug$T section. Currently llvm-objcopy only writes ELF files, so it would need to be taught to write COFF files. We have code to do this in the yaml2obj utility (specifically, in yaml2coff.cpp in the function writeCOFF). There may be a way to move this code to somewhere else (llvm/Object/COFF.h?) so that it can be re-used by both yaml2coff and llvm-objcopy, but in the worst case scenario you could copy the code and re-write it to work with these new structures. Lastly, you'll p...

...gt; >>>> On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> >>>> wrote: >>>> >>>>> You probably don't want to go down the same route that clang goes >>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>> the way clang does it will just give you a headache. There are multiple >>>>> abstractions involved to account for different object file formats (ELF, >>>>> COFF, MachO) and output formats (Assembly, binary file). At least with &gt...

...> On Sat, Jan 20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> >>>>> wrote: >>>>> >>>>>> You probably don't want to go down the same route that clang goes >>>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>>> the way clang does it will just give you a headache. There are multiple >>>>>> abstractions involved to account for different object file formats (ELF, >>>>>> COFF, MachO) and output formats (Assembly, binary file). At le...

Okay, apparently coff2yaml and yaml2coff are not in a great place as they both don't deal well with the fact that you can have overlapping sections, which seems to be what clang-cl produces (the .data section points to the same place as a later section). Which is not a big big problem for me particularly because msvc doesn't even...

...5 PM, Zachary Turner <zturner at google.com> >>>>>>> wrote: >>>>>>> >>>>>>>> You probably don't want to go down the same route that clang goes >>>>>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>>>>> the way clang does it will just give you a headache. There are multiple >>>>>>>> abstractions involved to account for different object file formats (ELF, >>>>>>>> COFF, MachO) and output formats (Assemb...

...20, 2018 at 9:05 PM, Zachary Turner <zturner at google.com> >>>>>> wrote: >>>>>> >>>>>>> You probably don't want to go down the same route that clang goes >>>>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>>>> the way clang does it will just give you a headache. There are multiple >>>>>>> abstractions involved to account for different object file formats (ELF, >>>>>>> COFF, MachO) and output formats (Assembly, binary f...

...ner <zturner at google.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> You probably don't want to go down the same route that clang goes >>>>>>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>>>>>> the way clang does it will just give you a headache. There are multiple >>>>>>>>> abstractions involved to account for different object file formats (ELF, >>>>>>>>> COFF, MachO) and output for...

...;>>>>>>> zturner at google.com> wrote: >>>>>>>>> >>>>>>>>>> You probably don't want to go down the same route that clang goes >>>>>>>>>> through to write the object file. If you think yaml2coff is convoluted, >>>>>>>>>> the way clang does it will just give you a headache. There are multiple >>>>>>>>>> abstractions involved to account for different object file formats (ELF, >>>>>>>>>> COFF, MachO) an...

...the > very least, we're not aware of any cases that don't work. > > Does your MSVC .obj file link fine before you add the .debug$H? > > On Fri, Jan 26, 2018 at 11:23 AM Leonardo Santagada <santagada at gmail.com> > wrote: > >> Okay, apparently coff2yaml and yaml2coff are not in a great place as they >> both don't deal well with the fact that you can have overlapping sections, >> which seems to be what clang-cl produces (the .data section points to the >> same place as a later section). Which is not a big big problem for me >> particu...

...;> zturner at google.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> You probably don't want to go down the same route that clang >>>>>>>>>>>> goes through to write the object file. If you think yaml2coff is >>>>>>>>>>>> convoluted, the way clang does it will just give you a headache. There are >>>>>>>>>>>> multiple abstractions involved to account for different object file formats >>>>>>>>>>>&g...

...;>>>> zturner at google.com> wrote: >>>>>>>>>> >>>>>>>>>>> You probably don't want to go down the same route that clang >>>>>>>>>>> goes through to write the object file. If you think yaml2coff is >>>>>>>>>>> convoluted, the way clang does it will just give you a headache. There are >>>>>>>>>>> multiple abstractions involved to account for different object file formats >>>>>>>>>>> (ELF, COF...

...ccept any MSVC .obj file to LLD. At the very least, we're not aware of any cases that don't work. Does your MSVC .obj file link fine before you add the .debug$H? On Fri, Jan 26, 2018 at 11:23 AM Leonardo Santagada <santagada at gmail.com> wrote: > Okay, apparently coff2yaml and yaml2coff are not in a great place as they > both don't deal well with the fact that you can have overlapping sections, > which seems to be what clang-cl produces (the .data section points to the > same place as a later section). Which is not a big big problem for me > particularly because ms...

...com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> You probably don't want to go down the same route that clang >>>>>>>>>>>>>> goes through to write the object file. If you think yaml2coff is >>>>>>>>>>>>>> convoluted, the way clang does it will just give you a headache. There are >>>>>>>>>>>>>> multiple abstractions involved to account for different object file formats >>>>>>>&g...

...r at google.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> You probably don't want to go down the same route that clang >>>>>>>>>>>>> goes through to write the object file. If you think yaml2coff is >>>>>>>>>>>>> convoluted, the way clang does it will just give you a headache. There are >>>>>>>>>>>>> multiple abstractions involved to account for different object file formats >>>>>>>>>&g...