search for: et_exec

...ie option? I'm OK if I have to link twice, first output DYN and then covert to EXEC in some way. Could you give some link command examples on it? lld\ELF\Writer.cpp static uint16_t getELFType() { if (Config->Pic) return ET_DYN; if (Config->Relocatable) return ET_REL; return ET_EXEC; } Thanks Steven -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190123/3d35f540/attachment.html>

I'm running into a completely different problem. When I do: opt -load LowerFastInvoke.o -help I get the message: Error opening 'LowerFastInvoke.o': LowerFastInvoke.o: only ET_DYN and ET_EXEC can be loaded? Am I missing something?

...6:37 AM, Kenneth Uildriks<kennethuil at gmail.com> wrote: > I'm running into a completely different problem.  When I do: > > opt -load LowerFastInvoke.o -help > > I get the message: > > Error opening 'LowerFastInvoke.o': LowerFastInvoke.o: only ET_DYN and > ET_EXEC can be loaded? > > Am I missing something? Assuming the extension is right, you're trying to load an object file, which isn't allowed; you have to link it first. -Eli

...nethuil at gmail.com> wrote: >> I'm running into a completely different problem.  When I do: >> >> opt -load LowerFastInvoke.o -help >> >> I get the message: >> >> Error opening 'LowerFastInvoke.o': LowerFastInvoke.o: only ET_DYN and >> ET_EXEC can be loaded? >> >> Am I missing something? > > Assuming the extension is right, you're trying to load an object file, > which isn't allowed; you have to link it first. > > -Eli > > _______________________________________________ > LLVM Developers mailin...

...ection use cases) * adding a SHF_ALLOC section is difficult. You likely need to fix the containing PT_LOAD segment. llvm-objcopy only does the base p_offset fix. You need to take care p_vaddr/p_paddr/p_filesz/p_memsz by your self. + adding a section smaller than the known lowest address (ET_EXEC with a non-zero image base) or larger than the known largest address: The PT_LOAD fixes are doable. + adding a section within the existing address ranges: this is very difficult due to many implicit inter-section references. If you have an advanced binary rewriting tool, this...

Thanks Bill! But it does not work. I get the error given below when I try to load LLVMExecutionEngine.o in the opt command. Error opening '../../../build/Release/lib/LLVMExecutionEngine.o': ../../../build/Release/lib/LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded -load request ignored. Any ideas?? Please help me out here. Thanks, Bhavani --- On Sun, 10/26/08, Bill Wendling <isanbard at gmail.com> wrote: > From: Bill Wendling <isanbard at gmail.com> > Subject: Re: [LLVMdev] Error while creating ExecutionEngine > To: b...

...use strict; sub PATH_MAX () {4096;} sub SZ_ELF32HDR () {52;} sub SZ_ELF64HDR () {64;} # Elf32_Ehdr->e_ident[4]: are variables 32 or 64 bit sub ELFCLASS32 () {1;} sub ELFCLASS64 () {2;} # Elf32_Ehdr->e_type: whether it's an executable, core, object # file or something else entirely. sub ET_EXEC () {2;} sub ET_DYN () {3;} # # ELF Private header # sub SZ_ELF32PHDR {32;} sub SZ_ELF64PHDR {56;} # Elf32_Phdr->p_type. sub PT_INTERP () {3;} # Program interpreter sub readStruct ($$$$$) { my ($fh, $off, $size, $pattern, $fieldNames) = @_; my @values; if (! seek ($fh, $off, 0)) { pri...

?The idea itself is indeed good. Regarding to escaping: I think we should have it. Imagine the following example (I've took it from D73828). --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2LSB Type: ET_EXEC Machine: EM_386 # RUN: yaml2obj %s --docnum=4 -D BITS=32 -o %t-32bit.o # RUN: yaml2obj %s --docnum=4 -D BITS=64 -o %t-64bit.o Without escaping it would be: Class: ELFCLASSBITS What does not look so clear as a version with escaping IMO. Best regards, George | Developer | Access Softek, In...

On Oct 25, 2008, at 9:51 PM, bhavani krishnan wrote: > Hi, > > I am completely new to llvm. I am trying to build an optimization > pass. I need to interpret some instructions in the pass. To begin > with, I used the exact same code as HowtoUseJIT example. It compiles > fine. While executing using opt, I get the following error at the > point where th executionengine

> Question: is there a good/quick/reliable way to figure out whether a > certain gcc compiler will mis-compile? http://llvm.org/docs/GettingStarted.html#brokengcc lists documented problems with different versions of gcc. I use gcc-4.3.2 with ubuntu 8.10 and haven't had any problems > 2. I ran into exactly the problem you pointed out. (Thank you) > The Makefile needs some update

Hello, use command : opt -load ../Release+Asserts/XX.o -XX <packetbuf.bc> /dev/null then I got the error by use the XX.o in the LLVM pass directory: Error opening "../Release+Asserts/XX.o" only ET_DYN and ET_EXEC can be loaded -load request ignored. I got another error by use the XX.o in the LLVM src directory $LLVM_SRC/Release+Asserts/lib/XX.o: Error opening '../../Release+Asserts/lib/XX.so': ../../Release+Asserts/lib/XX.so: undefined symbol: _ZN4llvm18EQTDDataStructures2IDE -load request ignor...

Hi, I am completely new to llvm. I am trying to build an optimization pass. I need to interpret some instructions in the pass. To begin with, I used the exact same code as HowtoUseJIT example. It compiles fine. While executing using opt, I get the following error at the point where th executionengine is created: opt: symbol lookup error: ../../../Release/lib/Try.so: undefined symbol:

Hey, LLVM has logic to parse ELF and PE binaries using `llvm::object::createBinary`. I tried to search in the codebase to see if there's a possibility to add/remove sections after parsing a binary and re-write the binary to another location. Basically, like what llvm-objcopy does. Can you point me to the right classes to look into, if this is something that LLVM has? Many thanks Joseph

Andrew did a great job of merging in the PDA->percpu changes and lguest code for 2.6.21-mm1, but the load_gdt is now unnecessary. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/lguest.c | 4 ---- 1 file changed, 4 deletions(-) =================================================================== --- a/drivers/lguest/lguest.c +++ b/drivers/lguest/lguest.c @@

Andrew did a great job of merging in the PDA->percpu changes and lguest code for 2.6.21-mm1, but the load_gdt is now unnecessary. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/lguest.c | 4 ---- 1 file changed, 4 deletions(-) =================================================================== --- a/drivers/lguest/lguest.c +++ b/drivers/lguest/lguest.c @@

Thanks, Shu, I guess I haven't updated since my post went out. There are actually 2 problems: 1. mis-compilation: My LLVM-2.5 turned out to be mis-compiled using gcc-4.4.0 (surprise to me) on Debian4-32b. I tried a few different compilers, and gcc-4.0.4 (a relatively old one, again surprised me) seems to work out fine. Question: is there a good/quick/reliable way to figure out whether a

I am adding -D k=v to yaml2obj, similar to clang -D. This makes it easy to generate {32-bit,64-bit} x {big-endian,little-endian} tests. --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2[[ENCODE]] Type: ET_DYN Machine: EM_X86_64 # RUN: yaml2obj -D BITS=32 -D ENCODE=LSB %s -o %t.32le # RUN: yaml2obj -D BITS=32 -D ENCODE=MSB %s -o %t.32le # RUN: yaml2obj

2012/1/23 Bendersky, Eli <eli.bendersky at intel.com>: > Hi, > > I would like to examine the implications you mention in more detail. > Thank you! > (1) Symbol address > According to the ELF standard, in a symbol table entry st_value means: "In relocatable files, st_value holds a section offset for a defined symbol. That is, > st_value is an offset from the

...int + # a message and you aren't supposed to be booting a + # bzImage directly from a floppy anyway. + + # e_ident + .byte ELFMAG0, ELFMAG1, ELFMAG2, ELFMAG3 + .byte ELFCLASS32, ELFDATA2LSB, EV_CURRENT, ELFOSABI_STANDALONE + .byte 0xeb, 0x3d, 0, 0, 0, 0, 0, 0 +#ifndef CONFIG_RELOCATABLE + .word ET_EXEC # e_type +#else + .word ET_DYN # e_type +#endif + .word EM_386 # e_machine + .int 1 # e_version + .int LOAD_PHYSICAL_ADDR # e_entry + .int phdr - bootsect_start # e_phoff + .int 0 # e_shoff + .int 0 # e_flags + .word e_ehdr - ehdr # e_ehsize + .word e_phdr1 - phdr #...

...int + # a message and you aren't supposed to be booting a + # bzImage directly from a floppy anyway. + + # e_ident + .byte ELFMAG0, ELFMAG1, ELFMAG2, ELFMAG3 + .byte ELFCLASS32, ELFDATA2LSB, EV_CURRENT, ELFOSABI_STANDALONE + .byte 0xeb, 0x3d, 0, 0, 0, 0, 0, 0 +#ifndef CONFIG_RELOCATABLE + .word ET_EXEC # e_type +#else + .word ET_DYN # e_type +#endif + .word EM_386 # e_machine + .int 1 # e_version + .int LOAD_PHYSICAL_ADDR # e_entry + .int phdr - bootsect_start # e_phoff + .int 0 # e_shoff + .int 0 # e_flags + .word e_ehdr - ehdr # e_ehsize + .word e_phdr1 - phdr #...