search for: getsectionnam

...t; output of the MCLoggingStreamer that may be enabled when outputting an > object file from llc or llvm-mc. It is broken into three pieces. > The first patch allows a MCSection to report a name to be used for > diagnostic purposes. I'm not sure if it may be a better idea to just make getSectionName virtual in the base class instead of adding a new getName function that just forwards to getSectionName in each subclass. Although getName is more consistent with the rest of the MC api. I propose that we make getSectionName virtual in the base class and then rename it to getName as it's more...

...ngStreamer that may be enabled when outputting an > > object file from llc or llvm-mc. It is broken into three pieces. > > The first patch allows a MCSection to report a name to be used for > > diagnostic purposes. > > I'm not sure if it may be a better idea to just make getSectionName > virtual in the base class instead of adding a new getName function > that just forwards to getSectionName in each subclass. Although > getName is more consistent with the rest of the MC api. > > I propose that we make getSectionName virtual in the base class and > then rename i...

Hi guys, Attached is a set of patches that adds detailed argument information to the output of the MCLoggingStreamer that may be enabled when outputting an object file from llc or llvm-mc. It is broken into three pieces. The first patch allows a MCSection to report a name to be used for diagnostic purposes. The second patch updates MCLoggingStreamer to enhance its output. This third patch

...be enabled when outputting an >> > object file from llc or llvm-mc. It is broken into three pieces. >> > The first patch allows a MCSection to report a name to be used for >> > diagnostic purposes. >> >> I'm not sure if it may be a better idea to just make getSectionName >> virtual in the base class instead of adding a new getName function >> that just forwards to getSectionName in each subclass. Although >> getName is more consistent with the rest of the MC api. >> >> I propose that we make getSectionName virtual in the base class an...

Hi, Thanks for pointing direction. As far, as I understand by reversing, logic, that I want to overwrite is digged into: lib/MC/MCSectionELF.cpp MCSectionELF::PrintSwitchToSection if (ShouldOmitSectionDirective(SectionName, MAI)) { OS << '\t' << getSectionName() << '\n'; return; } // otherwise print ".section" directive and then section name So I need to overwrite ShouldOmitSectionDirective behavior. But this method of MCSectionELF is not virtual. As a workaround, I stubbed it in core LLVM code (MCSectionELF::ShouldOmitSe...

This is a feature (or bug) of MCSectionELF::PrintSwitchToSection. For ELF target this function tries to escape string if it founds 'suspicious' character, see implementation in MCSectionELF.cpp: StringRef name = getSectionName(); if (name.find_first_not_of("0123456789_." "abcdefghijklmnopqrstuvwxyz" "ABCDEFGHIJKLMNOPQRSTUVWXYZ") == name.npos) { OS << "\t.section\t" << name; } else { OS << &quot...

...pointing direction. As far, as I understand by reversing, > logic, that I want to overwrite is digged into: > > lib/MC/MCSectionELF.cpp > > MCSectionELF::PrintSwitchToSection > > if (ShouldOmitSectionDirective(SectionName, MAI)) { > OS << '\t' << getSectionName() << '\n'; > return; > } > > // otherwise print ".section" directive and then section name > > So I need to overwrite ShouldOmitSectionDirective behavior. But this > method of MCSectionELF is not virtual. > As a workaround, I stubbed it in co...

...r 19, 2013 at 04:38:20PM +0700, Serge Pavlov wrote: > This is a feature (or bug) of MCSectionELF::PrintSwitchToSection. For > ELF target this function tries to escape string if it founds > 'suspicious' character, see implementation in MCSectionELF.cpp: > > StringRef name = getSectionName(); > if (name.find_first_not_of("0123456789_." > "abcdefghijklmnopqrstuvwxyz" > "ABCDEFGHIJKLMNOPQRSTUVWXYZ") == name.npos) { > OS << "\t.section\t" << name; > } els...

...ight idea about putting this in llvm-objcopy. You can look at one of the existing CopyBinary functions there, which currently only work for ELF, but you can just make a new overload that accepts a COFFObjectFile. I would probably start by iterating over each of the sections (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H sections. If you find a .debug$H section then you can just skip that object file. If you find a .debug$T but not a .debug$H, then basically do the same thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and pass it to GloballyHashedType::hash...

Hi, In the document: http://llvm.org/docs/WritingAnLLVMBackend.html described example like: SparcTargetAsmInfo::SparcTargetAsmInfo(const SparcTargetMachine &TM) { Data16bitsDirective = "\t.half\t"; Data32bitsDirective = "\t.word\t"; Data64bitsDirective = 0; // .xword is only supported by V9. ZeroDirective = "\t.skip\t"; CommentString = "!";

Hello > I really need in my backend value for this section, distinct from > default. Where can I set it? It was renamed to ReadOnlySection. You might want to check the logic inside CodeGen/TargetLoweringObjectFileImp.cpp (in particular - TargetLoweringObjectFile::SelectionSectionForGlobal) to see how it's used. -- With best regards, Anton Korobeynikov Faculty of Mathematics and

I'm going to file this bug but it's kind of a blocker for me so maybe someone has time to look at it. Should be nearly trivial to fix. It's a bug in the way the "section" attribute of functions is processed. Consider the following code: void x(int i) __attribute((section(".mySection,\"aw\", at progbits#"))); void x(int i) { } If you compile this

On Thu, Apr 18, 2013 at 06:57:29PM -0700, reed kotler wrote: > I'm going to file this bug but it's kind of a blocker for me so > maybe someone has time > to look at it. Should be nearly trivial to fix. I don't think this is a bug, but a misfeature in GCC due to the way it does (non-)escaping. Joerg

...lvm-objcopy. > > You can look at one of the existing CopyBinary functions there, which > currently only work for ELF, but you can just make a new overload that > accepts a COFFObjectFile. > > I would probably start by iterating over each of the sections > (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H > sections. > > If you find a .debug$H section then you can just skip that object file. > > If you find a .debug$T but not a .debug$H, then basically do the same > thing that LLD does in PDBLinker::mergeDebugT (create a CVTypeArray, and > pa...

...t; You can look at one of the existing CopyBinary functions there, which >> currently only work for ELF, but you can just make a new overload that >> accepts a COFFObjectFile. >> >> I would probably start by iterating over each of the sections >> (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H >> sections. >> >> If you find a .debug$H section then you can just skip that object file. >> >> If you find a .debug$T but not a .debug$H, then basically do the same >> thing that LLD does in PDBLinker::mergeDebugT (create a...

...opyBinary functions there, which >>>> currently only work for ELF, but you can just make a new overload that >>>> accepts a COFFObjectFile. >>>> >>>> I would probably start by iterating over each of the sections >>>> (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H >>>> sections. >>>> >>>> If you find a .debug$H section then you can just skip that object >>>> file. >>>> >>>> If you find a .debug$T but not a .debug$H, then basically do the same >>&...

...ne of the existing CopyBinary functions there, which >>> currently only work for ELF, but you can just make a new overload that >>> accepts a COFFObjectFile. >>> >>> I would probably start by iterating over each of the sections >>> (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H >>> sections. >>> >>> If you find a .debug$H section then you can just skip that object file. >>> >>> If you find a .debug$T but not a .debug$H, then basically do the same >>> thing that LLD does in PDBLinker:...

...there, which >>>>> currently only work for ELF, but you can just make a new overload that >>>>> accepts a COFFObjectFile. >>>>> >>>>> I would probably start by iterating over each of the sections >>>>> (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H >>>>> sections. >>>>> >>>>> If you find a .debug$H section then you can just skip that object >>>>> file. >>>>> >>>>> If you find a .debug$T but not a .debug$H, then basical...

...;>>>> currently only work for ELF, but you can just make a new overload that >>>>>> accepts a COFFObjectFile. >>>>>> >>>>>> I would probably start by iterating over each of the sections >>>>>> (getNumberOfSections / getSectionName) looking for .debug$T and .debug$H >>>>>> sections. >>>>>> >>>>>> If you find a .debug$H section then you can just skip that object >>>>>> file. >>>>>> >>>>>> If you find a .debug$T but not...

On Fri, Jan 19, 2018 at 9:44 PM, Zachary Turner <zturner at google.com> wrote: > > > On Fri, Jan 19, 2018 at 12:29 PM Leonardo Santagada <santagada at gmail.com> > wrote: > >> Hi, >> >> No I didn't, I used cl.exe from the visual studio toolchain. What I'm >> proposing is a tool for processing .obj files in COFF format, reading them