search for: pc32

Displaying 9 results from an estimated 9 matches for "pc32".

Did you mean: c32
2016 Oct 18
2
Proposal: arbitrary relocations in constant global initializers
...in/llc -filetype=obj -o - tc.ll -O3 > |~/src/llvm-build-rel/bin/llvm-objdump -d -r - > <stdin>: file format ELF64-x86-64 > > Disassembly of section .text: > bar: > 0: e9 00 00 00 00 jmp 0 <bar+5> > 0000000000000001: R_X86_64_PC32 foo-4-P > > > > Or on ARM: > > $ ~/src/llvm-build-rel/bin/llc -filetype=obj -o - tc.ll -O3 > -mtriple=armv7-unknown-linux |~/src/llvm-build-rel/bin/llvm-objdump -d -r - > > <stdin>: file format ELF32-arm-little > > Disassembly of section .text: &...
2015 Jul 29
0
[LLVMdev] Proposal: arbitrary relocations in constant global initializers
...) { tail call void @foo() ret void } $ ~/src/llvm-build-rel/bin/llc -filetype=obj -o - tc.ll -O3 |~/src/llvm-build-rel/bin/llvm-objdump -d -r - <stdin>: file format ELF64-x86-64 Disassembly of section .text: bar: 0: e9 00 00 00 00 jmp 0 <bar+5> 0000000000000001: R_X86_64_PC32 foo-4-P Or on ARM: $ ~/src/llvm-build-rel/bin/llc -filetype=obj -o - tc.ll -O3 -mtriple=armv7-unknown-linux |~/src/llvm-build-rel/bin/llvm-objdump -d -r - <stdin>: file format ELF32-arm-little Disassembly of section .text: bar: 0: fe ff ff ea b #-8 <bar> 00000000: R_AR...
2013 Dec 10
7
[PATCH] libxc/arm: Correctly handle the difference between virtual and physical address
...{ vcpu_guest_context_t *ctxt = ptr; + uint32_t rambase = dom->rambase_pfn << XC_PAGE_SHIFT; + uint32_t offset = dom->parms.virt_base - rambase; DOMPRINTF_CALLED(dom->xch); /* clear everything */ memset(ctxt, 0, sizeof(*ctxt)); - ctxt->user_regs.pc32 = dom->parms.virt_entry; + ctxt->user_regs.pc32 = dom->parms.virt_entry - offset; /* Linux boot protocol. See linux.Documentation/arm/Booting. */ ctxt->user_regs.r0_usr = 0; /* SBZ */ @@ -125,7 +127,7 @@ static int vcpu_arm32(struct xc_dom_image *dom, void *ptr) * l...
2020 Nov 02
2
[llvm-mc] FreeBSD kernel module performance impact when upgrading clang
...skeleton.o skeleton.o: file format elf64-x86-64 RELOCATION RECORDS FOR [.text]: OFFSET TYPE VALUE 0000000000000019 R_X86_64_32S .rodata.str1.1+0x0000000000000015 0000000000000024 R_X86_64_32S .rodata.str1.1+0x000000000000002b 000000000000002b R_X86_64_PC32 uprintf-0x0000000000000004 [...] clang10: $ objdump -r skeleton.o skeleton.o: file format elf64-x86-64 RELOCATION RECORDS FOR [.text]: OFFSET TYPE VALUE 0000000000000017 R_X86_64_32S .rodata.str1.1+0x000000000000002b 0000000000000020 R_X86_64_32S...
2003 Feb 11
0
samba 2.2.7a and multiple logins...
...nsfer fr users 5935 pc45 (192.168.1.45) Mon Feb 10 12:00:49 2003 jm jm users 6838 pc39 (192.168.1.39) Mon Feb 10 15:07:48 2003 IPC$ nobody nogroup 5124 pc53 (192.168.1.53) Mon Feb 10 14:01:04 2003 IPC$ nobody nogroup 10701 pc32 (192.168.1.66) Tue Feb 11 08:34:54 2003 IPC$ nobody nogroup 4833 pc40 (192.168.1.40) Mon Feb 10 08:01:15 2003 kr kr users 5813 pc33 (192.168.1.33) Mon Feb 10 11:28:39 2003 demo jm users 5902 pc39 (192.168.1.39) Mon Feb 10 11:52...
2020 Nov 05
0
[EXTERNAL] [llvm-mc] FreeBSD kernel module performance impact when upgrading clang
> You used -noinhibit-exec to ignore the diagnostic, which is usually a bad thing. I certainly agree with that. The point I was trying to make in my original email is that, specifically for kernel objects, this diagnostic is incorrect. R_X86_64_PC32 can be used safely against the symbol foo in that specific context, and should be possible without ignoring diagnostics. I wondered if there should be a way for the user to share that notion with the linker (my earlier "-mcmodel=kernel for the linker" comments). But I understand your poi...
2015 Jan 26
2
[LLVMdev] [llvm] r188726 - Adding PIC support for ELF on x86_64 platforms
...symbol offset to get it. + int64_t RealOffset = GOTAddr + Addend - SymOffset - FinalAddress; + assert(RealOffset <= INT32_MAX && RealOffset >= INT32_MIN); + int32_t TruncOffset = (RealOffset & 0xFFFFFFFF); + *Target = TruncOffset; + break; + } case ELF::R_X86_64_PC32: { // Get the placeholder value from the generated object since // a previous relocation attempt may have overwritten the loaded version @@ -240,6 +256,16 @@ void RuntimeDyldELF::resolveX86_64Reloca *Target = TruncOffset; break; } + case ELF::R_X86_64_PC64: { + // Get the...
2013 Jan 23
132
[PATCH 00/45] initial arm v8 (64-bit) support
First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I
2013 Feb 22
48
[PATCH v3 00/46] initial arm v8 (64-bit) support
This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.