Displaying 7 results from an estimated 7 matches for "r_386_pc32".
2006 Oct 23
1
error messages when rebuilding centosplus kernel
I'm rebuilding the centosplus kernel with ISA P&P and ISA some devies
enabled. At the very end of compilation, I got a lot of error
messages that looked like:
Error: ./init/initramfs.o .text refers to 0000046e R_386_PC32
.init.text
Error: ./init/initramfs.o .text refers to 0000059c R_386_PC32
.init.text
Error: ./init/initramfs.o .text refers to 000007a8 R_386_PC32
.init.text
Hmmm... Are these normal, or is there something wrong with the kernel build?
--
NOTICE: If you are not intended...
2018 Jun 05
2
lld mishandling R_X86_64_PC32 relocations
Hi,
I've tracked down what I believe is a bug in lld's relocation processing for R_X86_64_PC32 REL relocations.
I'm producing the object file in a slightly unusual way: I'm using objcopy on a relocatable i386 ELF object file to convert it to x86_64 which transforms a R_386_PC32 into a R_X86_64_PC32.
Steps to reproduce:
1. Assemble the attached bug.asm using nasm and note the R_386_PC32 REL.
$ nasm -felf32 -o bug.o bug.asm
$ x86_64-elf-objdump -dr bug.o | grep -A1 -e '<_start>:'
00000000 <_start>:
0: e8 fc ff ff ff call 1 <_start+0x1&g...
2008 Apr 26
3
extlinux: missing text on serial output
Hi!
Using the following extlinux.conf
serial 0x2f8 57600 0x013
# that is, RTS/CTS flow control on COM2
prompt 1
timeout 100
say Select 'linux' or 'xen'.
say Automatically booting 'xen' in 10 seconds.
default xen
label linux
kernel /vmlinuz-2.6.18-6-686
append initrd=/initrd.img-2.6.18-6-686 root=/dev/mapper/xen1-root ro console=tty0 console=ttyS1,57600n8r noresume
2020 Aug 21
3
[RFC][LLVM] New Constant type for representing function PLT entries
...ied)))
> * a PLT entry (other cases)
>
> The address can be insignificant: ultimately the program will call the
> function. There is no difference if the program calls the function
> directly or calls through one PLT entry in any module (executable or a
> shared object).
>
> R_386_PC32/R_X86_64_PC32/R_AARCH64_PREL32
Ignoring the ELF-specific bits, in essence, it's some dso-local function that's functionally equivalent to the actual resolved function at runtime. The address may or may not be equal to that of the resolved function.
Maybe it would make sense to introduce...
2011 Jul 01
2
[LLVMdev] Typo in IsLegalToCallImmediateAddr?
It seems that the || should be && here?
/// IsLegalToCallImmediateAddr - Return true if the subtarget allows calls
/// to immediate address.
bool X86Subtarget::IsLegalToCallImmediateAddr(const TargetMachine &TM) const {
if (Is64Bit)
return false;
return isTargetELF() || TM.getRelocationModel() == Reloc::Static;
}
For example, if you are doing ELF PIC (i.e. for a shared
2011 Jul 02
0
[LLVMdev] Typo in IsLegalToCallImmediateAddr?
...les without -fPIC:
---------------
int g(void) {
return 42;
}
--------------
int g(void);
int f(void) {
return g();
}
-------------
When they get combined into a .so, the code of f has:
452: e9 fc ff ff ff jmp 453 <f+0x7>
and readelf shows
00000453 00000802 R_386_PC32 00000458 g
so the dynamic linker will patch the code segment (making it non sharable)
So maybe the problem is that this function is being called in a place
that really wants a "IsProfitableToCallImmediateAddr"?
> - David
Cheers,
Rafael
2020 Aug 21
5
[RFC][LLVM] New Constant type for representing function PLT entries
I do have concerns about the amount of object level modeling that we want
to do in the IR though. While it isn't the highest level IR we've managed
to mostly avoid these kinds of features/complications in the past. I'm
definitely interested in hearing some alternate implementations here and
there rather than a full set of constants for relocations. Keeping the IR
abstract enough over