On 6 June 2015 at 19:12, Dan Olson via D.gnu wrote:
> "Iain Buclaw via D.gnu" writes:
>
> > On 6 June 2015 at 18:54, Dan Olson via D.gnu
> > wrote:
> >
> > "Iain Buclaw via D.gnu" writes:
> >
> > > Alas, after looking at backend, it turns out that the answer is
> > no.
> > >
>
"Iain Buclaw via D.gnu" writes:
> On 6 June 2015 at 18:54, Dan Olson via D.gnu
> wrote:
>
> "Iain Buclaw via D.gnu" writes:
>
> > Alas, after looking at backend, it turns out that the answer is
> no.
> >
> > In the glue sources (d-decls.cc), replace
> 'set_user_asse
On 6 June 2015 at 18:54, Dan Olson via D.gnu wrote:
> "Iain Buclaw via D.gnu" writes:
>
> > Alas, after looking at backend, it turns out that the answer is no.
> >
> > In the glue sources (d-decls.cc), replace 'set_user_assembler_name'
> > with 'SET_DECL_ASSEMBLER_NAME' and rebuild the module wi
"Iain Buclaw via D.gnu" writes:
> Alas, after looking at backend, it turns out that the answer is no.
>
> In the glue sources (d-decls.cc), replace 'set_user_assembler_name'
> with 'SET_DECL_ASSEMBLER_NAME' and rebuild the module without your
> workaround.
Ok, that works for data. Functions (st
On 6 June 2015 at 18:33, Iain Buclaw wrote:
> On 6 June 2015 at 18:18, Dan Olson via D.gnu wrote:
>
>> "Iain Buclaw via D.gnu" writes:
>>
>> > On 5 June 2015 at 08:40, Dan Olson via D.gnu
>> > wrote:
>> >>
>> >> Sorry for a long chain on OSX. But one last unresolved symbol from
>> > make
>> >>
On 6 June 2015 at 18:18, Dan Olson via D.gnu wrote:
> "Iain Buclaw via D.gnu" writes:
>
> > On 5 June 2015 at 08:40, Dan Olson via D.gnu
> > wrote:
> >>
> >> Sorry for a long chain on OSX. But one last unresolved symbol from
> > make
> >> check-d: "_d_osx_image_init". Is it just a placeholder o
"Iain Buclaw via D.gnu" writes:
> On 5 June 2015 at 08:40, Dan Olson via D.gnu
> wrote:
>>
>> Sorry for a long chain on OSX. But one last unresolved symbol from
> make
>> check-d: "_d_osx_image_init". Is it just a placeholder or is it
> hidden
>> somewhere. Does gdc still need the code to set se
On 6 June 2015 at 16:53, Dan Olson via D.gnu wrote:
> "Iain Buclaw via D.gnu" writes:
>
> > On 5 Jun 2015 08:05, "Dan Olson via D.gnu"
> > wrote:
> >
> > That's interesting, it should do that for you automatically, there
> > should be only one reason why that doesn't happen, and I don't use it
"Iain Buclaw via D.gnu" writes:
> On 5 Jun 2015 08:05, "Dan Olson via D.gnu"
> wrote:
>
> That's interesting, it should do that for you automatically, there
> should be only one reason why that doesn't happen, and I don't use it
> for pragma mangle.
That is what I expected too based on previous
"Iain Buclaw via D.gnu" writes:
> I hope I'm not shying you away by saying, this is what someone needs
> to find out.
No, not at all. I've gotten pretty used to puzzling through TLS
implementations for LDC porting.
> I'd first suggest to build gcc only and test what is outputted. Use a
> test p
On 5 Jun 2015 08:05, "Dan Olson via D.gnu" wrote:
>
> Dan Olson writes:
>
> > Looks like I need to track down missing symbols from rt.tlsgc now. I
> > think it is becoming a fun puzzle :-) The arm stuff can wait.
>
> How do I tell gdc that OS X needs target specific underscore "_" prefix
> added
On 5 June 2015 at 08:40, Dan Olson via D.gnu wrote:
>
> Sorry for a long chain on OSX. But one last unresolved symbol from make
> check-d: "_d_osx_image_init". Is it just a placeholder or is it hidden
> somewhere. Does gdc still need the code to set setup gc scanning? How
> is TLS on OSX? - if
http://bugzilla.gdcproject.org/show_bug.cgi?id=61
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
13 matches
Mail list logo
