https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106977
--- Comment #30 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to ibuclaw from comment #29) > (In reply to Iain Sandoe from comment #27) > > great! > > > > we make more progress now - at least past libphobos configure: > > > > we now fail building druntime/core/atomic.d and I am not quite sure how to > > interpret the backtrace (from b internal_error). > > > > d21`_D3dmd6access17checkSymbolAccessFPSQBh6dscope5ScopeCQBy7dsymbol7DsymbolZb > > (sc=<unavailable>, s=<unavailable>) at access.d:296 > > > My fear is that now it's corrupting the return in other ways now, this time > within D itself. I see.. that might be the tricky aspect of trying to have a different ABI internally and for accessing C/C++. Not sure how to solve it (are functions with C-family interfaces marked as such?)
