Re: versions for thumb and thumb-2 instruction sets

Mike writes: > On Wednesday, 10 February 2016 at 17:03:35 UTC, Dan Olson wrote: >> >> I noticed that even thumb-1 has different instruction set based on >> arm architecture. > > Yes. I did a little more research into this, as it peeked my > curiosity. Good info Mike. Thanks. > So, I still onl

Re: versions for thumb and thumb-2 instruction sets

Mike writes: > I think to do this properly with ARM you need to consider the ARM > architecture (ARMv6, ARMv7, ARMv7-A, ARMv7-M, etc..) AND the > instruction set (ARM or ARM_Thumb). I read it somewhere, but I'm > having trouble finding it again. > > Anyway, used in conjunction with the architectu

Re: versions for thumb and thumb-2 instruction sets

Timo Sintonen writes: > Thumb2 is an extension to thumb. It has everything that thumb has and > more. There is nothing in thumb that is not in thumb2. There is no > thumb1. Thumb is sometimes called thumb1 because thumb is often > understood to be both thumb and thumb2. > > Thumb2 was introduced t

versions for thumb and thumb-2 instruction sets

Hi Iain, Johannes. I'm asking here because I don't expect anybody else is playing with thumb instructions. Both GDC and LDC have version ARM_Thumb defined for original thumb (call it thumb-1) and thumb-2. But there is no way to tell in D code which set is supported. GCC and clang define these:

Targeting OS X (was Re: What gcc to use for gdc master?)

Seems to be working good now. Unittests for druntime all pass so Fiber switching code is working. Unittests for phobos fails in biguintcore, but I don't suppose that is an OS X specific thing. Iain, I am going to make separate pull requests for each OS X topic (fibers, symbol mangling, gc data s

Re: What gcc to use for gdc master?

"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. > >

Re: What gcc to use for gdc master?

"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

Re: What gcc to use for gdc master?

"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

Re: What gcc to use for gdc master?

"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

Re: What gcc to use for gdc master?

"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

Re: What gcc to use for gdc master?

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 not ready, would emutls work? -- Dan

Re: What gcc to use for gdc master?

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 to pragma(mangle, name)? thread.d uses core.internal.traits.exte

Re: What gcc to use for gdc master?

Dan Olson writes: > "Iain Buclaw via D.gnu" writes: > >> On 4 June 2015 at 17:33, Dan Olson via D.gnu >> wrote: >> >> As a sanity step before switching to gcc-6, tried to build gdc-5 >> branch >> on OSX X86_64

Re: What gcc to use for gdc master?

"Iain Buclaw via D.gnu" writes: > On 4 June 2015 at 17:33, Dan Olson via D.gnu > 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 > vers

Re: What gcc to use for gdc master?

"Iain Buclaw via D.gnu" 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

Re: What gcc to use for gdc master?

ketmar 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

What gcc to use for gdc master?

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