On 3 November 2015 at 11:07, mattcoder via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> On Sunday, 1 November 2015 at 02:36:16 UTC, Manu wrote:
>>
>> ...
>> Does it support Dreamcast? :P
>
>
> I don't know if you are being serious here but if yes... what's the catch with Dreamcast? I mean this is a Fan thing or what?

I'm just a massive nerd, and the Dreamcast was a great console! :P

Am Tue, 3 Nov 2015 09:16:47 +1000
schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:

> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd like to annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.

But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed). If you're talking about running tests on the x86_64 architecture that should be easy.

On Tuesday, 3 November 2015 at 07:30:44 UTC, Johannes Pfau wrote:
> Am Tue, 3 Nov 2015 09:16:47 +1000
> schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:
>
>> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd like to annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.
>
> But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed). If you're talking about running tests on the x86_64 architecture that should be easy.

There's a Dreamcast emulator for Android/ARM:

https://github.com/reicast/reicast-emulator

You could run it inside the Android emulator on Travis: :)

http://docs.travis-ci.com/user/languages/android/

I'm sure their servers can handle an emulator of a 200 MHz MIPS core with 16 MB of RAM running inside an ARM emulator. ;)

On Tuesday, 3 November 2015 at 08:36:46 UTC, Joakim wrote:
> There's a Dreamcast emulator for Android/ARM:
>
> https://github.com/reicast/reicast-emulator
>
> You could run it inside the Android emulator on Travis: :)
>
> http://docs.travis-ci.com/user/languages/android/
>
> I'm sure their servers can handle an emulator of a 200 MHz MIPS core with 16 MB of RAM running inside an ARM emulator. ;)

Whoops, it runs on linux/x64 also, no need for the Android intermediary.

On 3 November 2015 at 17:30, Johannes Pfau via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> Am Tue, 3 Nov 2015 09:16:47 +1000
> schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:
>
>> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd like to annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.
>
> But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed). If you're talking about running tests on the x86_64 architecture that should be easy.

Emulators are the typical approach. Even Android + iOS have emulators
that can be used for CI.
Most emulators have such features required to return runtime errors
back to the host environment for this sort of testing.

On 3 November 2015 at 18:36, Joakim via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> On Tuesday, 3 November 2015 at 07:30:44 UTC, Johannes Pfau wrote:
>>
>> Am Tue, 3 Nov 2015 09:16:47 +1000
>> schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:
>>
>>> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd like to annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.
>>
>>
>> But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed). If you're talking about running tests on the x86_64 architecture that should be easy.
>
>
> There's a Dreamcast emulator for Android/ARM:
>
> https://github.com/reicast/reicast-emulator
>
> You could run it inside the Android emulator on Travis: :)
>
> http://docs.travis-ci.com/user/languages/android/
>
> I'm sure their servers can handle an emulator of a 200 MHz MIPS core with 16 MB of RAM running inside an ARM emulator. ;)

For the record, I was mostly joking about Dreamcast ;) ... while I did
support it actively some years back, I haven't built that code in a
while. It would be a lot of fun to get it working again though :P
Incidentally, there's a GCC dev that's been committing SIMD
optimisations for the SH4 (Dreamcast) backend recently. He's obviously
having some fun making all the vector intrinsics work with the DC
hardware.
Latest GCC is the best Dreamcast compiler we've ever had!

Am Wed, 4 Nov 2015 09:40:42 +1000
schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:

> On 3 November 2015 at 18:36, Joakim via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> > On Tuesday, 3 November 2015 at 07:30:44 UTC, Johannes Pfau wrote:
> >>
> >> Am Tue, 3 Nov 2015 09:16:47 +1000
> >> schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:
> >> 
> >>> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd like to annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.
> >>
> >>
> >> But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed). If you're talking about running tests on the x86_64 architecture that should be easy.
> >
> >
> > There's a Dreamcast emulator for Android/ARM:
> >
> > https://github.com/reicast/reicast-emulator
> >
> > You could run it inside the Android emulator on Travis: :)
> >
> > http://docs.travis-ci.com/user/languages/android/
> >
> > I'm sure their servers can handle an emulator of a 200 MHz MIPS core with 16 MB of RAM running inside an ARM emulator. ;)
> 
> For the record, I was mostly joking about Dreamcast ;) ... while I did
> support it actively some years back, I haven't built that code in a
> while. It would be a lot of fun to get it working again though :P
> Incidentally, there's a GCC dev that's been committing SIMD
> optimisations for the SH4 (Dreamcast) backend recently. He's obviously
> having some fun making all the vector intrinsics work with the DC
> hardware.
> Latest GCC is the best Dreamcast compiler we've ever had!

The Dreamcast is SH4 based? IIRC there are some regressions in recent GCC builds for SH4 but it's being resurrected as the Open Processor Foundation now develops open source SH processors:

http://lwn.net/Articles/647636/ http://0pf.org/about-ocf.html

On 4 November 2015 at 00:40, Manu via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> On 3 November 2015 at 18:36, Joakim via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> > On Tuesday, 3 November 2015 at 07:30:44 UTC, Johannes Pfau wrote:
> >>
> >> Am Tue, 3 Nov 2015 09:16:47 +1000
> >> schrieb Manu via Digitalmars-d <digitalmars-d@puremagic.com>:
> >>
> >>> I have a samples directory which it would be theoretically possible to run and see that they don't crash as part of a test run. Also, I'd
> like to
> >>> annotate my whole engine quite comprehensively with unittests. It's something that I'm keen to work on, and then it further helps to assure those toolchains remain working.
> >>
> >>
> >> But how exactly would you run these? All CI machines are x86_64. I guess emulators could be a possibility as long as they run headless. We'd need some way to get feedback from the emulator though (test passed/failed).
> If
> >> you're talking about running tests on the x86_64 architecture that
> should be
> >> easy.
> >
> >
> > There's a Dreamcast emulator for Android/ARM:
> >
> > https://github.com/reicast/reicast-emulator
> >
> > You could run it inside the Android emulator on Travis: :)
> >
> > http://docs.travis-ci.com/user/languages/android/
> >
> > I'm sure their servers can handle an emulator of a 200 MHz MIPS core
> with 16
> > MB of RAM running inside an ARM emulator. ;)
>
> For the record, I was mostly joking about Dreamcast ;) ... while I did
> support it actively some years back, I haven't built that code in a
> while. It would be a lot of fun to get it working again though :P
> Incidentally, there's a GCC dev that's been committing SIMD
> optimisations for the SH4 (Dreamcast) backend recently. He's obviously
> having some fun making all the vector intrinsics work with the DC
> hardware.
> Latest GCC is the best Dreamcast compiler we've ever had!
>

I'm aware of this, not because I take an interest, but because I was cc'd into discussion when they discovered a C++ regression that was seen by comparing the md5sum of (D frontend) interpret.c sources between 2nd and 3rd generation bootstrapped builds.  ;-)

If you don't understand why, that's because this file contains all frontend const folding routines for every operation on every basic type supported in D, and then some.  So itself becomes a good stress test of a compiler's codegen ability (or in this case, the ability to produce consistent code).

On Tuesday, 3 November 2015 at 04:10:57 UTC, Manu wrote:
> On 3 November 2015 at 11:07, mattcoder via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>> On Sunday, 1 November 2015 at 02:36:16 UTC, Manu wrote:
>>>
>>> ...
>>> Does it support Dreamcast? :P
>>
>>
>> I don't know if you are being serious here but if yes... what's the catch with Dreamcast? I mean this is a Fan thing or what?
>
> I'm just a massive nerd, and the Dreamcast was a great console! :P

By the way, since it's called fuji, I assume it runs on Atari. ;)

On 4 November 2015 at 18:34, Adrian Matoga via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> On Tuesday, 3 November 2015 at 04:10:57 UTC, Manu wrote:
>>
>> On 3 November 2015 at 11:07, mattcoder via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>>>
>>> On Sunday, 1 November 2015 at 02:36:16 UTC, Manu wrote:
>>>>
>>>>
>>>> ...
>>>> Does it support Dreamcast? :P
>>>
>>>
>>>
>>> I don't know if you are being serious here but if yes... what's the catch with Dreamcast? I mean this is a Fan thing or what?
>>
>>
>> I'm just a massive nerd, and the Dreamcast was a great console! :P
>
>
> By the way, since it's called fuji, I assume it runs on Atari. ;)

Hah! That's really pushing the limits!
I did write some little Atari2600 games once... we even did a 2600
demo comp once ;)
Terrible machine!