similar to: question about --emit-relocs with lld

Folks, This question is somewhat related to a previous posting of mine. I just can't seem to create a generic solution. Here is a function that I found searching around the internet: splitIt <- function(x, n) {split(x, sort(rank(x) %% n))} I use it like so: > splitIt(1:12, 2) $`0` [1] 1 2 3 4 5 6 $`1` [1] 7 8 9 10 11 12 Or > splitIt(1:12, 4) $`0` [1] 1 2 3 $`1` [1] 4 5 6

Hi, Now in case of relocatable object generation LLD merges and copies REL/RELA sections as is and does not touch any addends. But it is incorrect. If we have a relocation which targets a section, we have to adjust the relocation's addend to take in account that the section might be merged with other ones. Here is the reproduction script: % cat t1.s .data .long 0 .text bar: movl $1,

Hi, I'm in the process of migrating from clang5 to clang10. Unfortunately clang10 introduced a negative performance impact. The cause is an increase of PLT entries from this patch (first released in clang7): https://bugs.llvm.org/show_bug.cgi?id=36370 https://reviews.llvm.org/D43383 If I revert that clang patch locally, the additional PLT entries and the performance impact disappear. This

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

Hi, I am trying to compile R with the command below in order to install rpy2. ./configure --prefix=/usr/local/R/R-2.9.2 --with-gnu-ld --with-cairo --with-x --enable-R-shlib However, error the I have gotten was: /usr/bin/ld: CConverters.o: relocation R_X86_64_32S against `R_FunTab' can not be used when making a shared object; recompile with -fPIC CConverters.o: could not read symbols: Bad

Hi, Zvi, I agree. In the context of targeting the KNL, however, I'm a bit concerned about the addressing, and specifically, the size of the resulting encoding: > vmovdqu32 zmm0, zmmword ptr [rax + c+401280] ;load b[401280] in > zmm0 > > vpaddd zmm1, zmm1, zmmword ptr [rax + b+401344] > ; zmm1<-zmm1+b[401344] The KNL can only

> 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

I have just installed dovecot and want to set up the drac interface. However, when I compile drac.c I get the following link errors; anybody know what the right compile options are for a 64 bit system? I have a Gentoo Linux system using the amd64 architecture. gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac

On 2009-03-06 22:18, David Greene wrote: > Thanks to Daniel, we have a new home for the validator buildbot. Thanks, > Daniel! > > Go to http://google1.osuosl.org:8080 and have a look. > Looks like the x86_64 buildsbots are failing:

Thanks to Daniel, we have a new home for the validator buildbot. Thanks, Daniel! Go to http://google1.osuosl.org:8080 and have a look. -Dave

Hi, I cannot compile R with shared library. I am using Redhad Linux on Dell hardware. Here''s what I am doing: I set ?PICFLAGS in config.site file: CPICFLAGS=-fPIC FPICFLAGS=-fPIC and issue: ./configure --enable-R-shlib --prefix=$HOME/newR make configure finishes with no complaints, the last informative line being: Options enabled: shared R library, shared BLAS, R

Code: https://godbolt.org/z/T397fo I'm running some performance experiments on a x86-64 linux system, where I've modified LLVM to reserve a register, and I'd like to use that register in my code. Currently, I'm using %r12d, which is callee save, so I don't need to worry about compatibility with existing libraries or system calls. For security reasons, the generated binaries

On Wednesday 11 March 2009 15:47, Török Edwin wrote: > > Go to http://google1.osuosl.org:8080 and have a look. > > Looks like the x86_64 buildsbots are failing: > > /.AUTO/cray/iss.compiler/cost/tools/llvm-tools/x86_64-unknown-linux-gnu/bin >/../lib/gcc/x86_64-unknown-linux-gnu/4.1.2/../../../../x86_64-unknown-linux- >gnu/bin/ld: >

Ok so now I'm getting this when doing a make in asterisk... travis at pcimphone1:~/downloads/asterisk-13.5.0$ make [LD] chan_pjsip.o pjsip/dialplan_functions.o -> chan_pjsip.so /usr/bin/ld: /usr/local/lib/libpjsip-ua-x86_64-unknown-linux-gnu.a(sip_inv.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

Hello, I am trying to compile Samba4 on RHEL 5.3 which didn't have Python on it. I've downloaded Python-2.6.5.tar from http://ftp.samba.org/pub/tridge/python/. I get the following error during the compile : .......................................... ........................................... [3285/3758] Compiling lib/krb5_wrap/enctype_convert.c [3286/3758] Linking

Hello, I am facing a problem when rebuilding Samba 3.4.8dfsg2 on Debian Testing. Command used: "dpkg-buildpackage -uc -us -rfakeroot --source-option=--format=1.0" Linking bin/smbcontrol /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/libunwind-ptrace.a(_UPT_access_fpreg.o): relocation R_X86_64_32S against `_UPT_reg_offset' can not be used when making a shared

Hi all, I am having some some trouble with LLVM 3.8... I built it with GCC 4.8.2 with cmake and no special CXX/C flags. That means in case of GCC that RTTI is switched on, I believe. However, building my MCJIT application against the just built LLVM and linking results in: libqdp.a(qdp_llvm.o):(.rodata._ZTIN4llvm8FCmpInstE[_ZTIN4llvm8FCmpInstE]+0x10): undefined reference to `typeinfo for

Hi Ahmed, >From what can be seen in the code snippet you provided, the reuse of XMM0 and XMM1 across loop-unroll instances does not inhibit instruction-level parallelism. Modern X86 processors use register renaming that can eliminate the dependencies in the instruction stream. In the example you provided, the processor should be able to identify the 2-vloads + vadd + vstore sequences as

On Mon, Feb 13, 2017 at 05:34:01PM -0500, Waiman Long wrote: > It is the address of &steal_time that will exceed the 32-bit limit. That seems extremely unlikely. That would mean we have more than 4G worth of per-cpu variables declared in the kernel.

On Mon, Feb 13, 2017 at 05:34:01PM -0500, Waiman Long wrote: > It is the address of &steal_time that will exceed the 32-bit limit. That seems extremely unlikely. That would mean we have more than 4G worth of per-cpu variables declared in the kernel.