<div class="gmail_quote">On Mon, Jun 4, 2012 at 4:31 AM, Matthew Caron <span dir="ltr"><<a href="mailto:Matt.Caron@redlion.net" target="_blank">Matt.Caron@redlion.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">

<div class="im">On 06/01/2012 10:13 PM, Andrew Wiley wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div class="im">
On Fri, Jun 1, 2012 at 3:24 PM, Alex Rønne Petersen <<a href="mailto:alex@lycus.org" target="_blank">alex@lycus.org</a><br></div><div class="im">
<mailto:<a href="mailto:alex@lycus.org" target="_blank">alex@lycus.org</a>>> wrote:<br>
    Please try building libphobos and libdruntime with -fno-section-anchors.<br>
<br>
<br>
You certainly need to do this, but -O0 means that section-anchors<br>
optimization is turned off anyway, so that isn't actually your problem.<br>
</div></blockquote>
<br>
Judging by:<br>
<br>
<a href="https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm" target="_blank">https://bitbucket.org/goshawk/<u></u>gdc/issue/120/fsection-<u></u>anchors-broken-on-arm</a><br>
<br>
(specifically <a href="https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm#comment-686378" target="_blank">https://bitbucket.org/goshawk/<u></u>gdc/issue/120/fsection-<u></u>anchors-broken-on-arm#comment-<u></u>686378</a>), I thought that was fixed.<br>


<br>
I guess not. I'll build it with no-section-anchors from now on.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
Can you run `disassemble` in gdb to see what the faulting instruction is?<br>
</blockquote>
<br>
<br></div>
(gdb) disassemble<br>
Dump of assembler code for function _<u></u>D2gc3gcx3Gcx16fullcollectshell<u></u>MFZk:<br>
0x00045358 <_<u></u>D2gc3gcx3Gcx16fullcollectshell<u></u>MFZk+0>:     push    {r4, r5, r6, r7, r8, r9, r10, r11, lr}<br>
0x0004535c <_<u></u>D2gc3gcx3Gcx16fullcollectshell<u></u>MFZk+4>:     vstmdb  sp!, {d8-d15}<br></blockquote><div> </div><div>You're faulting on a VFP instruction. What hardware are you trying to target, and what is the output of `gdc -v` and `gcc -v` ?</div>

<div> </div></div>