similar to: Question about the example of link time optimization

Hi the list In the DESCRIPTION file of my package foo0, I have: Depends: foo1 Imports: foo2 Suggest: foo3 Enhence: foo4 If I understand correctly, to install foo0 on my computer, I need to already have foo1, foo2, foo3. foo4 is not necessary. I my R sesssion, when I will write: library(foo0), then the package foo1 will be attach. foo2, foo3 and foo4 will not. Is that correct? But what is

Hi All, I compiled the following code on my linux PC using clang with PIE option- struct struct4 {char a; char b; char c; char d; }; struct struct4 foo4 = {'a','2','c','4'}; struct struct4 fun4() { return foo4; } int main() { fun4(); return 0; } > clang -g -fPIE structs.c In GDB session when i call p/c fun4() i get something like below- (gdb) p/c

# ./imaptest host=127.0.0.1 port=143 user=tstem38 pass=pass4you mbox=/ gpfs/users/t/s/tstem38/IMAP/foo4 Panic: file client.c: line 620: assertion failed: (idx >= array_count(&clients) == NULL) IOT/Abort trap(coredump) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2541 bytes Desc: not available

> On May 17, 2016, at 1:33 AM, Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > Let me ask a LTO simple question again. For the llvm LTO example in the link:http://llvm.org/docs/LinkTimeOptimization.html <http://llvm.org/docs/LinkTimeOptimization.html>, I use below build commands to generate three different optimization level binary: -O0, -O1, -O2.

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program

Dear R Helpers, I am trying to find a way to identify all the objects in my environment that are all caps and then end with .f. I can do the all caps part pretty easily, but I have tried a number of variations on the \ and can't get a recognition of that operator. As a simple example A.f<-"foo1" AA.f<-"foo2" aa.f<-"foo3" A.a<-"foo4" ls()

Hi Pavel, thank you for you response. objdump -T showed that there are no symbols defined in liblldb.so. After few compilations I found that problem is with linking with LLD (-DLLVM_ENABLE_LLD=ON) without the directive everything is ok. Hana ============= $ objdump -T lib64/liblldb.so lib64/liblldb.so: file format elf64-x86-64 DYNAMIC SYMBOL TABLE: 0000000000000000 w D *UND*

On 2020-11-11, Alexandre Bique wrote: >It did partially fix the issue but there is still one problem: > >llvm-objdump -sx gives: > >Version References: > required from libpthread.so.0: > 0x09691a75 0x00 05 GLIBC_2.2.5 > 0x09691972 0x00 09 GLIBC_2.3.2 > 0x09691973 0x00 07 GLIBC_2.3.3 > 0x06969192 0x00 12 GLIBC_2.12 > required from libdl.so.2: >

This did the job: patchelf --clear-symbol-version log Podolski.64.so Alexandre Bique On Wed, Nov 11, 2020 at 2:19 PM Alexandre Bique <bique.alexandre at gmail.com> wrote: > > On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote: > > > How to find what is pulling libmvec? > > > > If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can

It did partially fix the issue but there is still one problem: llvm-objdump -sx gives: Version References: required from libpthread.so.0: 0x09691a75 0x00 05 GLIBC_2.2.5 0x09691972 0x00 09 GLIBC_2.3.2 0x09691973 0x00 07 GLIBC_2.3.3 0x06969192 0x00 12 GLIBC_2.12 required from libdl.so.2: 0x09691a75 0x00 21 GLIBC_2.2.5 required from libuuid.so.1: 0x09da27b0 0x00 19

On Tue, Nov 10, 2020 at 7:01 PM Fāng-ruì Sòng <maskray at google.com> wrote: > > How to find what is pulling libmvec? > > If you build a -DCMAKE_BUILD_TYPE=Debug lld, you can set a breakpoint > on lld/ELF/MarkLive.cpp:114 (ss->getFile().isNeeded) and check which > symbol makes > libmvec.so needed. I'm afraid this is going to far for me :) > > On the other

Hi, So I managed to install llvm 11 on the server and got more information thank to your help: Projects/Podolski/CMakeFiles/Podolski.dir/__/__/AudioModulesFrame/AM_WavLoader.cpp.o: reference to exp Projects/Podolski/CMakeFiles/Podolski.dir/__/__/libs/tinyexpr/tinyexpr.c.o: reference to exp Projects/Podolski/CMakeFiles/Podolski.dir/__/__/AudioModulesFrame/AM_PitchTrack.cpp.o: reference to exp

On Wed, Oct 28, 2020 at 6:07 PM Fangrui Song <maskray at google.com> wrote: > > On 2020-10-28, Alexandre Bique via llvm-dev wrote: > >Hi, > > > >I wonder what is the right way to target an old glibc? > > > >I have a machine which is up to date (glibc 2.32 and clang+lld 10.0.1). > > > >So far I've been able to target older glibc by having a

Hi, I wonder what is the right way to target an old glibc? I have a machine which is up to date (glibc 2.32 and clang+lld 10.0.1). So far I've been able to target older glibc by having a C file containing: __asm__(".symver powf,powf at GLIBC_2.2.5"); __asm__(".symver expf,expf at GLIBC_2.2.5"); __asm__(".symver exp2f,exp2f at GLIBC_2.2.5");

On Mon, Nov 9, 2020 at 9:39 AM Alexandre Bique <bique.alexandre at gmail.com> wrote: > > Hi, > > So I managed to install llvm 11 on the server and got more information > thank to your help: > > Projects/Podolski/CMakeFiles/Podolski.dir/__/__/AudioModulesFrame/AM_WavLoader.cpp.o: > reference to exp >

This is just a note/wishlist/for the record: With foo1 <- function() { res; } foo2 <- function() { for (i in c()) res <- 1; res; } foo3 <- function() { while (FALSE) res <- 1; res; } foo4 <- function() { if (FALSE) res <- 1; res; } we get: > foo1() Error in foo1() : object 'res' not found > foo2() Error in foo2() : object 'res' not

https://bugzilla.netfilter.org/show_bug.cgi?id=842 Summary: Addition of iptables rule referencing an ipset of the wrong address family does not fail Product: ipset Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: default

> On Mar 24, 2016, at 12:45 PM, Xiangyang Guo via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > When I define an intrinsic function with memory write permission, my assumption is that we can either attach [IntrReadWriteArgMem] or [] to the intrinsic function. Based on the comment of the source code , "IntrReadWriteArgMem - This intrinsic reads and writes

Oh, this might be the issue - yum says it can't open "nvidia-x11-drv-304xx-304.135-1.el6.elrepo.x86_64.rpm" - let me download it again and see what happens. Are there md5 hash sums on these files? On Thu, Feb 8, 2018 at 3:23 PM, Phil Perry <pperry at elrepo.org> wrote: > On 08/02/18 15:10, Felipe Westfields wrote: > >> I copied the error message exactly as it

On Tue, Nov 10, 2020 at 12:27 AM Alexandre Bique <bique.alexandre at gmail.com> wrote: > > Thank you very much for your help Fāng-ruì Sòng. > > I've tried various things like linking directly to libm-2.32 but it > didn't work, it seems that libm-2.32 still pulls libmvec. > > I have the following linker flags: > > CLANG_LDFLAGS="-fuse-ld=lld