search for: weakrefer

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 alias to declarations and they are a

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 >

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

On Wed, 23 Aug 2006, nathan r. hruby wrote: > On Thu, 24 Aug 2006, John 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

> 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

Hi Sitvanit, On 12/07/12 22:18, Sitvanit Ruah wrote: > I ran "configure -help " and it says > > usage: configure [OPTION]..... [VAR=VALUE] > > So I assume configure CC=... is the right syntax. Isn't it? while you might think so, try it the other way round. Also, by doing make VERBOSE=1 you can see which compiler is really being used. Ciao, Duncan. > >

I ran "configure -help " and it says usage: configure [OPTION]..... [VAR=VALUE] So I assume configure CC=... is the right syntax. Isn't it? Regard, Sitvanit From: Konstantin Tokarev <annulen at yandex.ru> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: llvmdev-bounces at cs.uiuc.edu, llvmdev at cs.uiuc.edu, Duncan Sands <baldrick at free.fr> Date:

Hi, My brother (Tarun) and I have been attempting to get dragonegg working 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

Hi, I am new to LLVM, so I am sorry if the question I am going to ask has already been raised before. I will be thankful if anyone can describe me a quick way to search relevant topics within the list archive, When I am trying to compile a simple code, containing access to std::string, with clang: #include <string> int main() { std::string s; return

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

Hello all, I am new to this mailing list so I hope this is the right place to post the following question. We are considering using Clang front end for our tool. 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+

Hi, I am trying to run the bigmemory example provided on the http://www.bigmemory.org/ The example runs on the "airline data" and generates summary of the csv files:- library(bigmemory) library(biganalytics) x <- read.big.matrix("2005.csv", type="integer", header=TRUE, backingfile="airline.bin", descriptorfile="airline.desc",

I tried CC=gcc44 CXX=g++44 ../llvm/configure and got CC=gcc44: Command not found So the syntax is indeed as wriiten in the help. Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel: 972-4-828-1249 From: Duncan Sands <baldrick at free.fr> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: Konstantin Tokarev <annulen at yandex.ru>, llvmdev at cs.uiuc.edu,

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

In this email to the R-help list: https://stat.ethz.ch/pipermail/r-help/2017-June/447474.html and in this question on Stackoverflow: https://stackoverflow.com/questions/44486643/nleqslv-memory-use-in-r Andrew Leach has raised a question about the memory usage of my package nleqslv. In a model with a loop within a function he has experienced continuously increasing memory usage by package nleqslv

It's undocumented FAQ, if you are using RHEL5 (or clone). - install gcc44-c++ - Build with CC=gcc44 CXX=g++44 - You may need "CC=clang -std=gnu89" to use clang with its glibc. Have fun! ps. AFAIK, clang can be built more easily on centos6. ...Takumi 2012/7/11 Sitvanit Ruah <RUAH at il.ibm.com>: > > Hello all, > I am new to this mailing list so I hope this is

Thanks for the information. I am running on a machine on which gcc44 is installed but whose default installation is 4.1.2. 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).. I tried also ../llvm/configure CC=gcc44 CXX=g++44 --include_dir=<gcc44 include dir> but it didn't help

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.

Hi Is there a way of finding out when or whether the wx object referenced in ruby is still alive? Here''s my problem # register that +wx_control+ should update on application events of type +event_type+ def add_subscriber(wx_control, app_event_type) @subscriptions[app_event_type].push(wx_control) end # later def broadcast(app_event) @subscriptions[app_event.type].each { |

The Asterisk Development Team has announced the release of Asterisk 11.19.0-rc1. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 11.19.0-rc1 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: