Displaying 3 results from an estimated 3 matches for "dummysymbol".
2009 Dec 04
2
[LLVMdev] r72619
Hi Duncan,
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"));
}
The c'tor for std::string is emitted as code from llvm-gcc. It is then
inlined. And a weak external for the `_S_construct' variable is
created. However, C++ rules stipulate that it shouldn't be, because of
explicit & imp...
2009 Dec 04
0
[LLVMdev] r72619
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"));
> }
>
> The c'tor for std::string is emitted as code from llvm-gcc. It is then
> inlined. And a weak external for the `_S_construct' variable is created.
> However, C++ rules stipulate that it shouldn't be, beca...
2009 Dec 04
2
[LLVMdev] r72619
...2: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"));
>> }
>> The c'tor for std::string is emitted as code from llvm-gcc. It is
>> then inlined. And a weak external for the `_S_construct' variable
>> is created. However, C++ rules stipulate that it shouldn...