search for: weakref

A long time ago (before r97733) we used to model the weakref attribute by outputting a new declaration and a weak alias to it. This was fairly buggy and we now implement weakref directly in clang, with the same logic an assembler uses to implement .weakref (which is what gcc prints). One thing that was left from that old implementation is that we still have...

On Oct 30, 2013, at 12:35 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > A long time ago (before r97733) we used to model the weakref attribute > by outputting a new declaration and a weak alias to it. This was > fairly buggy and we now implement weakref directly in clang, with the > same logic an assembler uses to implement .weakref (which is what gcc > prints). This makes sense to me, but I'm not an expert on E...

On 30 October 2013 15:50, Chris Lattner <clattner at apple.com> wrote: > > On Oct 30, 2013, at 12:35 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> A long time ago (before r97733) we used to model the weakref attribute >> by outputting a new declaration and a weak alias to it. This was >> fairly buggy and we now implement weakref directly in clang, with the >> same logic an assembler uses to implement .weakref (which is what gcc >> prints). > > This makes sense to me, but I...

...ohn Summerfield wrote: > > > nathan r. hruby wrote: > > > > > I have a user running RT on a RHEL4 machine. He recently did the RHEL4.4 > > > update and now it appears that the Tree::Simple module (a requirement of > > > RT) is broken, as it was built with weakref support that was in a prior > > > perl package and it appears that the new perl-5.8.5-36 package has lost > > > that support. > > > > > > Red Hat Bugzilla has nothing about this particular issue that I can find. > > > Anyone else experienced this? >...

> Yes, it is the same error referring to 4.1.2. > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref > declaration must have internal > linkage > __gthrw(pthread_key_delete) > > There are several such errors. Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g++44 ../llvm/configure instead? -- Regards, Konstantin

...12 05:09 PM > Subject: Re:[LLVMdev] Compiling llvm and Clang on Linux > > > > > >> Yes, it is the same error referring to 4.1.2. >> >> /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ >> +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref >> declaration must have internal >> linkage >> __gthrw(pthread_key_delete) >> >> There are several such errors. > > Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g+ > +44 ../llvm/configure instead? > > -- > Regards, > K...

...lt;baldrick at free.fr> Date: 12/07/2012 05:09 PM Subject: Re:[LLVMdev] Compiling llvm and Clang on Linux > Yes, it is the same error referring to 4.1.2. > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref > declaration must have internal > linkage > __gthrw(pthread_key_delete) > > There are several such errors. Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g+ +44 ../llvm/configure instead? -- Regards, Konstantin

...ing with gcc-5 and llvm-3.6. So far we have had some success and most of the compilator and validator tests of dragonegg pass. However the following validator tests fail and we don't understand why. The Validator :: c++/2007-01-06-ELF-Thunk-Sections.cpp The Validator :: c/ExternFunctionWeakref.c The Validator :: c/ExternVariableWeakref.c The Validator :: c/InternFunctionWeakref.c The Validator :: c/InternVariableWeakref.c Since the last four are extremely similar, I give the example of ExternVariableWeakref.c below: The test file looks like: // RUN: %dragonegg -S %s -o - |...

...++/4.1.2/x86_64-redhat-linux/bits/c++io.h:38: In file included from /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/x86_64-redhat-linux/bits/gthr.h:132: /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/x86_64-redhat-linux/bits/gthr-default.h:100:68: error: weakref declaration must have internal linkage extern __typeof(pthread_once) __gthrw_pthread_once __attribute__ ((__weakref__("pthread_once"))); In one of the development phorums, I found somebody saying that LLVM does not support gcc 4.1 libraries. Is that true? If yes, which libraries sh...

Hi all, Recently I have upgraded a Python application from Xapian 1.0.7 to 1.2.2 in order to use the PostingSource class. It is a long-running process, and I am seeing the number of open file descriptors to the Xapian database steadily increase. I suspect what I am seeing is some kind of resource leak. I have no idea if it is a problem in our code or in the Xapian Python bindings. How do I debug

...I tried to compile LLVM (using configure followed by make from the llvm top directory) on LINUX X86 with gcc 4.1.2. I got several compilation error messages of the form /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ +/4.1.2/i386-redhat-linux/bits/gthr-default.h:117:1: error: weakref declaration must have internal linkage __gthrw(pthread_mutexattr_destroy) Could you guide me on how to resolve these errors? I downloaded the sources from the web page (not from SVN). Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory

...builtin char logical integer 121940 178 1600 15068 9518 8981 double complex character ... any list 7983 17 47593 0 0 4073 expression bytecode externalptr weakref raw S4 2 0 618 117 119 1838 Anyone who has previously worked with bigmemory before could throw some light on it. Were you able to run the examples successfully? Thanks in advance. Harsh Yadav [[alternative HTML version delet...

...05:09 PM > Subject: Re:[LLVMdev] Compiling llvm and Clang on Linux > > > > > >> Yes, it is the same error referring to 4.1.2. >> >> /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ >> +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref >> declaration must have internal >> linkage >> __gthrw(pthread_key_delete) >> >> There are several such errors. > > Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g+ > +44 ../llvm/configure instead? > > -- > Regards, > K...

I'm trying to build an app with clang against libraries that are using GCC 4.1 ABI. I'm getting an error "weakref declaration must have internal linkage" Now I'm stumped though, perhaps it is an incompatibility between clang trunk and gcc 4.1 include files? - I've built clang from trunk - fixed include paths to point to gcc 4.1 include paths When I modify clang to use gcc 4.5 include files, the...

...builtin char logical integer 51374 45 671 9786 8030 37258 double complex character ... any list 2645 1 53795 0 0 18487 expression bytecode externalptr weakref raw S4 1 14662 2233 592 593 1049 > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 416340 22.3 750400 40.1 581181 31.1 Vcells 726127 5.6 1308461 10.0 1191521 9.1 > print(paste("At end memory used is&q...

...onfigure followed by make from the llvm top directory) on LINUX > X86 with gcc 4.1.2. > > I got several compilation error messages of the form > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:117:1: error: > weakref declaration must have internal linkage > __gthrw(pthread_mutexattr_destroy) > > Could you guide me on how to resolve these errors? > I downloaded the sources from the web page (not from SVN). > Thanks, > Sitvanit > > > Sitvanit Ruah > Formal Verification Group > IBM...

...onfigure followed by make from the llvm top directory) on LINUX > X86 with gcc 4.1.2. > > I got several compilation error messages of the form > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:117:1: error: > weakref declaration must have internal linkage > __gthrw(pthread_mutexattr_destroy) > > Could you guide me on how to resolve these errors? > I downloaded the sources from the web page (not from SVN). > Thanks, > Sitvanit > > > Sitvanit Ruah > Formal Verification Group > IBM...

Hi, > I ran > ../llvm/configure CC=gcc44 CXX=g++44 > make > > and still got the same error (I checked and CC=gcc44 and CXX=g++44 now in > build/Makefile.config).. is it exactly the same error? The original error referred to gcc-4.1 header files. Does the new error still refer to gcc-4.1 header files, or is it now talking about gcc-4.4 header files? Ciao, Duncan.

...ill in the subscribers list. When an event is broadcast, its "notify" method is called, it gives a "pure virtual method call" error (wxruby 0.6.0). I''ve tried several different things to clean up the subscribers list as controls are destroyed, but without success: WeakRef ObjectSpace.define_finalizer(subscriber) subscriber.evt_close() { | e | delete_subscriber(subscriber) } The last seems to be the most promising, but it doesn''t work for all the control types that can be subscribers - only for frames. Is there something universal to all Wx controls that...

...ssful call dialog match (Reported by Damian Ivereigh) * ASTERISK-25139 - Malicious transfer sequence locks up Asterisk (Reported by Gregory Massel) * ASTERISK-25094 - PBX core: Investigate thread safety issues (Reported by Corey Farrell) * ASTERISK-22559 - gcc 4.6 and higher supports weakref attribute but asterisk doesn't detect it. (Reported by ibercom) * ASTERISK-24717 - ASAN: global-buffer-overflow codec_{ilbc | gsm | adpcm | ipc10} (Reported by Badalian Vyacheslav) * ASTERISK-25100 - asterisk coredump if host has an IPv6 address that end with ::80 (Reported...