search for: writesect

...a8 (dynamic relocation r_addend) points to a function at .text segment (in this case frame_dummy). I am trying to made this on lld, but current step sequence is: - Write::run \_ Write::createSections \_ Write::scanRelocs \_ Write::addReloc // Dynamic Relocation creation \_ Write::writeSections \_ OutputSectionBase::writeTo \_ InputSection::writeTo \_ InputSection::relocate \_ TargetInfo::relocateOne The problem is only at TargetInfo::relocate the target (aarch64) will see that the relocation is a R_AARCH64_ABS64 one and thus will need to create...

...; So I think you just need to write the bytes immediately after the >>>>> coff::symbol. The thing you need to write looks like a >>>>> coff::coff_aux_section_definition structure. >>>>> >>>>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks >>>>> like its a CRC32 of the actual section contents, which you can generate >>>>> with a couple of lines of code: >>>>> >>>>> JamCRC JC(/*Init=*/0); >>>>> JC.update(DebugHContents); >>>>>...

...just need to write the bytes immediately after the >>>>>> coff::symbol. The thing you need to write looks like a >>>>>> coff::coff_aux_section_definition structure. >>>>>> >>>>>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It >>>>>> looks like its a CRC32 of the actual section contents, which you can >>>>>> generate with a couple of lines of code: >>>>>> >>>>>> JamCRC JC(/*Init=*/0); >>>>>> JC.update(DebugHContents); &g...

...ite the bytes immediately after the >>>>>>> coff::symbol. The thing you need to write looks like a >>>>>>> coff::coff_aux_section_definition structure. >>>>>>> >>>>>>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It >>>>>>> looks like its a CRC32 of the actual section contents, which you can >>>>>>> generate with a couple of lines of code: >>>>>>> >>>>>>> JamCRC JC(/*Init=*/0); >>>>>>> JC.update...

I''ve run a little wired benchmark on comparing Btrfs v0.19 and XFS: There are 2000 directories and each directory contains 1000 files. The workload randomly stat a file or chmod a file for 2000000 times. And the number of stat and chmod are 50% and 50%. I monitor the number of disk read requests #Disk Write Requests, #Disk Read Requests, #Disk Write Sectors, #Disk Read

...mediately after the >>>>>>>> coff::symbol. The thing you need to write looks like a >>>>>>>> coff::coff_aux_section_definition structure. >>>>>>>> >>>>>>>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It >>>>>>>> looks like its a CRC32 of the actual section contents, which you can >>>>>>>> generate with a couple of lines of code: >>>>>>>> >>>>>>>> JamCRC JC(/*Init=*/0); >>>>>>...

One remaining blocking issue for linking FreeBSD with lld is the inability to build the bootloader components. We have a patch[1] in review to address one of the problems by switching to using a linker script instead of GNU ld's -N option. Another issue is that some bootloader components are created by the linker directly as binary objects, using --oformat binary. (Other bootloader components

...>>>> So I think you just need to write the bytes immediately after the >>>> coff::symbol. The thing you need to write looks like a >>>> coff::coff_aux_section_definition structure. >>>> >>>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks >>>> like its a CRC32 of the actual section contents, which you can generate >>>> with a couple of lines of code: >>>> >>>> JamCRC JC(/*Init=*/0); >>>> JC.update(DebugHContents); >>>> AuxSymbol.CheckSum = JC...

...olSize; >>> >>> So I think you just need to write the bytes immediately after the >>> coff::symbol. The thing you need to write looks like a >>> coff::coff_aux_section_definition structure. >>> >>> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks >>> like its a CRC32 of the actual section contents, which you can generate >>> with a couple of lines of code: >>> >>> JamCRC JC(/*Init=*/0); >>> JC.update(DebugHContents); >>> AuxSymbol.CheckSum = JC.getCRC(); >>>...

...Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + SymbolSize; So I think you just need to write the bytes immediately after the coff::symbol. The thing you need to write looks like a coff::coff_aux_section_definition structure. For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks like its a CRC32 of the actual section contents, which you can generate with a couple of lines of code: JamCRC JC(/*Init=*/0); JC.update(DebugHContents); AuxSymbol.CheckSum = JC.getCRC(); Hope this helps On Thu, Jan 25, 2018 at 10:46 AM Leonardo Santagada <santagada at gma...

...st uint8_t *>(Symbol.getRawPtr()) + > SymbolSize; > > So I think you just need to write the bytes immediately after the > coff::symbol. The thing you need to write looks like a > coff::coff_aux_section_definition structure. > > For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks > like its a CRC32 of the actual section contents, which you can generate > with a couple of lines of code: > > JamCRC JC(/*Init=*/0); > JC.update(DebugHContents); > AuxSymbol.CheckSum = JC.getCRC(); > > Hope this helps > > On Thu, Jan 25, 2018 at 1...

...awPtr()) + >> SymbolSize; >> >> So I think you just need to write the bytes immediately after the >> coff::symbol. The thing you need to write looks like a >> coff::coff_aux_section_definition structure. >> >> For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks >> like its a CRC32 of the actual section contents, which you can generate >> with a couple of lines of code: >> >> JamCRC JC(/*Init=*/0); >> JC.update(DebugHContents); >> AuxSymbol.CheckSum = JC.getCRC(); >> >> Hope this helps &gt...

I see that there is an auxsymbol per section symbol, and also on the yaml representation there is a checksum, selection and unused all of them I have no idea how to fill in, also this aux symbol might have some important information for me to patch on the other symbols. Can you find the part in llvm that it writes those? because at least for auxsymbol the yaml part of the code threats as a binary