<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.CodeBlock, li.CodeBlock, div.CodeBlock
{mso-style-name:"Code Block";
margin:0in;
margin-bottom:.0001pt;
background:#F2F2F2;
font-size:11.0pt;
font-family:Consolas;}
p.MailQuote, li.MailQuote, div.MailQuote
{mso-style-name:"Mail Quote";
margin:0in;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal" style="text-align:justify">I posted a variant of this query on llvm-dev and haven’t got any response yet. I am looking for hints on what could be the cause for the following error:<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="CodeBlock">`__clang_call_terminate' referenced in section `.text' of some_file.o: defined in discarded section `.text.__clang_call_terminate[__clang_call_terminate]' of some_file.o<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">The clang version is 3.8.1 running on redhat 5 and x86_64 (yes, I know…older linux kernel, but clang 3.4 works without issues on the same platform). The above error occurs only when -g is used (possibly the reference
to __clang_call_terminate gets removed when optimizations are enabled). There is another issue (a run-time crash in the executable generated by clang that I am trying to debug and that is when the above error was exposed).<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">I see that __clang_call_terminate shows up as a weak symbol in libc++abi. The executable I am building uses -static-libgcc and -static-libstdc++ options on link line (clang++ is invoked on the link line). libc++
or libc++abi are not used.<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">In case, it is relevant, the clang++ compiler that I am using was first built from release_38 branch using g++ 4.8.3 and libstdc++ (libc++/c++abi are also built in this step) and then I rebuilt clang++ with the
clang++ and libc++/libc++abi from the previous step. It is the clang++ in the second that we are using. I have not tried to use clang++ from the first step to compile our code.<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">I have tried to create a standalone test case for the above issue but has not been successful. If you can provide any hints to possible causes, it would help in coming up with a test case. Specifically, I would
like to know what C++ code can result in the generation of __clang_call_terminate. I suspect it has something to do with exceptions (std::terminate??). I couldn’t find any documentation on this. I can look at the clang source code but that is going to take
me more time.<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">-Riyaz<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>