Starting a pull request for ARM and grabbed gdc master, but not sure what gcc it likes.  I tried gcc-5.1 but

$ ./setup-gcc.sh ../gcc-5.1.0
found gcc version 5
This version of GCC (5) is not supported.

-- 
Dan

On Thu, 04 Jun 2015 00:15:37 -0700, Dan Olson wrote:

> Starting a pull request for ARM and grabbed gdc master, but not sure what gcc it likes.  I tried gcc-5.1 but
> 
> $ ./setup-gcc.sh ../gcc-5.1.0 found gcc version 5 This version of GCC
> (5) is not supported.

make sure that you switched to 'gdc-5' branch.

ketmar <ketmar@ketmar.no-ip.org> writes:

> On Thu, 04 Jun 2015 00:15:37 -0700, Dan Olson wrote:
>
>> Starting a pull request for ARM and grabbed gdc master, but not sure what gcc it likes.  I tried gcc-5.1 but
>> 
>> $ ./setup-gcc.sh ../gcc-5.1.0 found gcc version 5 This version of GCC
>> (5) is not supported.
>
> make sure that you switched to 'gdc-5' branch.

Does gdc-5 get folded back into master then, isn't it a release branch? I assume pull requests should be based on master?

On 4 June 2015 at 15:49, Dan Olson via D.gnu <d.gnu@puremagic.com> wrote:

> ketmar <ketmar@ketmar.no-ip.org> writes:
>
> > On Thu, 04 Jun 2015 00:15:37 -0700, Dan Olson wrote:
> >
> >> Starting a pull request for ARM and grabbed gdc master, but not sure what gcc it likes.  I tried gcc-5.1 but
> >>
> >> $ ./setup-gcc.sh ../gcc-5.1.0 found gcc version 5 This version of GCC
> >> (5) is not supported.
> >
> > make sure that you switched to 'gdc-5' branch.
>
> Does gdc-5 get folded back into master then, isn't it a release branch? I assume pull requests should be based on master?
>

All PRs should be based on master, and they get trickled down to release branches as needed.

Master only works (or at least, has been tested) with the development snapshot listed in gcc.version.  Which would be version gcc-6 now.

On Thu, 04 Jun 2015 06:49:00 -0700, Dan Olson wrote:

> ketmar <ketmar@ketmar.no-ip.org> writes:
> 
>> On Thu, 04 Jun 2015 00:15:37 -0700, Dan Olson wrote:
>>
>>> Starting a pull request for ARM and grabbed gdc master, but not sure what gcc it likes.  I tried gcc-5.1 but
>>> 
>>> $ ./setup-gcc.sh ../gcc-5.1.0 found gcc version 5 This version of GCC
>>> (5) is not supported.
>>
>> make sure that you switched to 'gdc-5' branch.
> 
> Does gdc-5 get folded back into master then, isn't it a release branch? I assume pull requests should be based on master?

master is for upcoming gcc6.

"Iain Buclaw via D.gnu" <d.gnu@puremagic.com> writes:

> All PRs should be based on master, and they get trickled down to release branches as needed.
>
> Master only works (or at least, has been tested) with the development snapshot listed in gcc.version. Which would be version gcc-6 now.

Ok, thanks.

As a sanity step before switching to gcc-6, tried to build gdc-5 branch on OSX X86_64 with gcc-5.1.  I must be missing something because no versions are satisfied for thread.d fiber_switchContext().  Should D_InlineAsm_X86* versions be defined in GDC?  They are not in my build.

Making all in libdruntime
/Users/dan/projects/gdc-dev/gdc/objdir/./gcc/gdc -B/Users/dan/projects/gdc-dev/gdc/objdir/./gcc/ -B/Users/dan/projects/gdc-dev/install/x86_64-apple-darwin14.3.0/bin/ -B/Users/dan/projects/gdc-dev/install/x86_64-apple-darwin14.3.0/lib/ -isystem /Users/dan/projects/gdc-dev/install/x86_64-apple-darwin14.3.0/include -isystem /Users/dan/projects/gdc-dev/install/x86_64-apple-darwin14.3.0/sys-include -o core/thread.o -Wall -Werror -g -frelease -O2 -nostdinc -pipe -Wno-deprecated -I ../../../../gcc-5.1.0/libphobos/libdruntime -I ./x86_64-apple-darwin14.3.0 -I .  -c ../../../../gcc-5.1.0/libphobos/libdruntime/core/thread.d
../../../../gcc-5.1.0/libphobos/libdruntime/core/thread.d:3550:13: error: static assert  "Not implemented"
             static assert(0, "Not implemented");

On 4 June 2015 at 17:33, Dan Olson via D.gnu <d.gnu@puremagic.com> wrote:

> "Iain Buclaw via D.gnu" <d.gnu@puremagic.com> writes:
>
> > All PRs should be based on master, and they get trickled down to release branches as needed.
> >
> > Master only works (or at least, has been tested) with the development snapshot listed in gcc.version. Which would be version gcc-6 now.
>
> Ok, thanks.
>
> As a sanity step before switching to gcc-6, tried to build gdc-5 branch on OSX X86_64 with gcc-5.1.  I must be missing something because no versions are satisfied for thread.d fiber_switchContext().  Should D_InlineAsm_X86* versions be defined in GDC?  They are not in my build.
>
>
No.  Someone should port them to Asm_External and implement it in thread.S

This should be trivial except for the X32 target, which needs to be looked at for the correct way to switch fibers.

"Iain Buclaw via D.gnu" <d.gnu@puremagic.com> writes:

> On 4 June 2015 at 17:33, Dan Olson via D.gnu <d.gnu@puremagic.com>
> wrote:
> 
>     As a sanity step before switching to gcc-6, tried to build gdc-5
>     branch
>     on OSX X86_64 with gcc-5.1. I must be missing something because no
>     versions are satisfied for thread.d fiber_switchContext(). Should
>     D_InlineAsm_X86* versions be defined in GDC? They are not in my
>     build.
> 
> 
>
> No. Someone should port them to Asm_External and implement it in thread.S
>
> This should be trivial except for the X32 target, which needs to be looked at for the correct way to switch fibers.

Are you saying gdc doesn't currently build a native compiler on OS X? Why do I think I built it before?  Foggy memory...

Dan Olson <gorox@comcast.net> writes:

> "Iain Buclaw via D.gnu" <d.gnu@puremagic.com> writes:
>
>> On 4 June 2015 at 17:33, Dan Olson via D.gnu <d.gnu@puremagic.com>
>> wrote:
>> 
>>     As a sanity step before switching to gcc-6, tried to build gdc-5
>>     branch
>>     on OSX X86_64 with gcc-5.1. I must be missing something because no
>>     versions are satisfied for thread.d fiber_switchContext(). Should
>>     D_InlineAsm_X86* versions be defined in GDC? They are not in my
>>     build.
>> 
>> 
>>
>> No. Someone should port them to Asm_External and implement it in thread.S
>>
>> This should be trivial except for the X32 target, which needs to be looked at for the correct way to switch fibers.
>
> Are you saying gdc doesn't currently build a native compiler on OS X? Why do I think I built it before?  Foggy memory...

Ok, I have these in threadasm.S now, compiler cranking away. Trying check-d ...

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.

Dan Olson <gorox@comcast.net> 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 to pragma(mangle, name)?  thread.d uses core.internal.traits.externDFunc.  That is cause.  For now I worked around with:

pragma(mangle, "_"~mangleFunc!T(fqn)) mixin(decl);