On Mon, Jun 4, 2012 at 4:31 AM, Matthew Caron <matt.ca...@redlion.net>wrote:
> On 06/01/2012 10:13 PM, Andrew Wiley wrote: > >> On Fri, Jun 1, 2012 at 3:24 PM, Alex Rønne Petersen <a...@lycus.org >> <mailto:a...@lycus.org>> wrote: >> Please try building libphobos and libdruntime with >> -fno-section-anchors. >> >> >> You certainly need to do this, but -O0 means that section-anchors >> optimization is turned off anyway, so that isn't actually your problem. >> > > Judging by: > > https://bitbucket.org/goshawk/**gdc/issue/120/fsection-** > anchors-broken-on-arm<https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm> > > (specifically https://bitbucket.org/goshawk/**gdc/issue/120/fsection-** > anchors-broken-on-arm#comment-**686378<https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm#comment-686378>), > I thought that was fixed. > > I guess not. I'll build it with no-section-anchors from now on. > > > Can you run `disassemble` in gdb to see what the faulting instruction is? >> > > > (gdb) disassemble > Dump of assembler code for function _**D2gc3gcx3Gcx16fullcollectshell** > MFZk: > 0x00045358 <_**D2gc3gcx3Gcx16fullcollectshell**MFZk+0>: push {r4, > r5, r6, r7, r8, r9, r10, r11, lr} > 0x0004535c <_**D2gc3gcx3Gcx16fullcollectshell**MFZk+4>: vstmdb sp!, > {d8-d15} > 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` ?
