search for: _z11dummysymbolv

...gt; > there are several functions in the example you sent, some linkonce > and some > available_externally. Which ones shouldn't be there and why? Can > you please > give more details about why it is a problem - it was kind of hand- > wavy so > far :) > Only "_Z11dummysymbolv" should be there. Here's Doug's explanation of why this should be so: Here's what it *looks* like is happening, and where the FE is probably getting it wrong. First of all, the constructor in question is defined outside of the basic_string class template as a non-inline defi...

>> > Only "_Z11dummysymbolv" should be there. Here's Doug's explanation of > why this should be so: > > Here's what it *looks* like is happening, and where the FE is probably > getting it wrong. First of all, the constructor in question is defined > outside of the basic_string class temp...

Hi Bill, > Here's what I get with TOT compiling with -Os. The orig.ll is what I get > before r72619. Notice that orig.ll has only one function in it. Both the > one you sent and duncan.ll have more than one function. It's not the > fact that more than one function is showing up, but these functions in > particular shouldn't be there because of the implicit/explicit

On Dec 4, 2009, at 2:40 PM, Eric Christopher wrote: >>> >> Only "_Z11dummysymbolv" should be there. Here's Doug's explanation of >> why this should be so: >> >> Here's what it *looks* like is happening, and where the FE is >> probably >> getting it wrong. First of all, the constructor in question is >> defined >> out...

On Dec 4, 2009, at 12:52 AM, Duncan Sands wrote: > Hi Bill, > >> There's a problem with your check-in for r72619 is causing "weak >> external" symbols to appear in C++ code when it shouldn't. Take >> this code for example, >> #include <stdexcept> >> void dummysymbol() { >> throw(std::runtime_error("string"));