search for: targetloweringobjectfileimpl

...on’t coalesce it because it is named. So, is >> there a way to keep the named values in the __const section? >> > > I believe the following patch would be the minimal needed to do this, > there is some dead code that could be removed as well. > > diff --git a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > index 55e1756..bf78ce1 100644 > --- a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > +++ b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > @@ -667,12 +667,6 @@ > TargetLoweringObjectFileMachO::getSectionForConstant(SectionKind...

...eFunction const&)", referenced from: llvm::DwarfDebug::endFunction(llvm::MachineFunction const*)in libLLVMAsmPrinter.a(DwarfDebug.cpp.o) "typeinfo for llvm::TargetLoweringObjectFile", referenced from: typeinfo for llvm::TargetLoweringObjectFileELFin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) typeinfo for llvm::TargetLoweringObjectFileMachOin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) typeinfo for llvm::TargetLoweringObjectFileCOFFin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) "llvm::GuaranteedTailCallOpt", referenced from: __ZN4ll...

...eFunction const&)", referenced from: llvm::DwarfDebug::endFunction(llvm::MachineFunction const*)in libLLVMAsmPrinter.a(DwarfDebug.cpp.o) "typeinfo for llvm::TargetLoweringObjectFile", referenced from: typeinfo for llvm::TargetLoweringObjectFileELFin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) typeinfo for llvm::TargetLoweringObjectFileMachOin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) typeinfo for llvm::TargetLoweringObjectFileCOFFin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) "llvm::GuaranteedTailCallOpt", referenced from: __ZN4ll...

On Aug 25, 2014, at 8:26 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > On 21 August 2014 19:32, Akira Hatanaka <ahatanak at gmail.com> wrote: >> Is there a way to distinguish between GlobalValues that are user-defined and >> those that are compiler-defined? I am looking for a function that I can use >> to tell if a GlobalValue is user-defined ,

...Actually, the strings appear together inside a .rodata.str1.1 section instead of getting their own section. It seems that the C-string literal are considered differently than other constant and the -fdata-sections is not respected in https://github.com/llvm/llvm-project/blob/master/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp#L799. [1] I came across the following GCC bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=192 where they have fixed the issue back in 2015. Any reason not to do so in LLVM? My code example: - static library 1 : expose functions api1() and api3() > #include "lib1.h" > >...

Hello, I'm implementing a port of LLVM for PowerPC VLE. It's a compressed instruction set similar to mips16 and ARM Thumb. Instruction encoding (VLE/non-vle) is selected for a given memory region by an attribute in a memory area descriptor. Targets supporting this that I know of are all bare-metal (so powerpc-none-elf). I'm trying to implement ELF support right now. VLE ELF files

...hecking on loads, stores, and other memory intrinsics. FunctionPass *createBoundsCheckingPass(); +ModulePass *createCFGProfilePass(); + /// \brief Calculate what to divide by to scale counts. /// /// Given the maximum count, calculate a divisor that will scale all the diff --git a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp index 6922e33..9f786b0 100644 --- a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp +++ b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp @@ -97,16 +97,48 @@ void TargetLoweringObjectFileELF::emitModuleMetadata( StringRef Section; GetObjCImageInf...

On Wed, 2010-05-05 at 13:22 -0700, Nathan Jeffords wrote: > > The important point here is that the COFF MCSection needs to > have the right level of semantic information. In fact, > MCSection is the place that I'd start for COFF bringup. > > OK, I see that now. The current isolation > between TargetLoweringObjectFile ->

Reported https://bugs.llvm.org/show_bug.cgi?id=38911 Thanks, Leslie Zhai 在 2018年09月11日 16:55, Dimitry Andric 写道: > Hi Leslie, > > The problem really lies in the OpenJDK code, as it is attempting to > write to a const object. If this seems to work with certain compiler(s) > and optimization settings, it is just luck. :-) > > Here is a reduced example, which shows the

...CodeGen/SelectionDAG.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/SelectionDAGISel.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/SelectionDAGNodes.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/SlotIndexes.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/TargetLoweringObjectFileImpl.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/ValueTypes.h -- Installing: /usr/local/llvm-2.8/include/llvm/CodeGen/ValueTypes.td -- Installing: /usr/local/llvm-2.8/include/llvm/CompilerDriver -- Installing: /usr/local/llvm-2.8/include/llvm/CompilerDriver/Action.h -- Installing: /usr/loc...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel

...rts build llvm[2]: Compiling TailDuplication.cpp for Release+Asserts build llvm[2]: Compiling TargetFrameLoweringImpl.cpp for Release+Asserts build llvm[2]: Compiling TargetInstrInfo.cpp for Release+Asserts build llvm[2]: Compiling TargetLoweringBase.cpp for Release+Asserts build llvm[2]: Compiling TargetLoweringObjectFileImpl.cpp for Release+Asserts build llvm[2]: Compiling TargetOptionsImpl.cpp for Release+Asserts build llvm[2]: Compiling TargetRegisterInfo.cpp for Release+Asserts build llvm[2]: Compiling TargetSchedule.cpp for Release+Asserts build llvm[2]: Compiling TwoAddressInstructionPass.cpp for Release+Asserts b...