[llvm-dev] Clang for the PlayStation 2

[Dan Ravensloft via llvm-dev]

I have a GitHub page containing my patches and a rough writeup of the
issues I've encountered at https://github.com/ZirconiumX/ps2-clang-patches

There's still a *lot* of work to be done before I'm going to consider
upstreaming the backend, if at all, but I'll do my best to get bugfixes
sorted quickly.

On Sun, 16 Sep 2018, 18:10 xkrebstarx, <xkrebstarx at gmail.com> wrote:

> Hi Dan,
>
> This is pretty interesting. Do you have a project page (or something) that
> I can check out?
>
> On Sep 16, 2018, at 05:34, Dan Ravensloft via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> I've been somewhat busy with life over the past week, but I thought I'd
> come back to this all the same.
>
> On Sat, 8 Sep 2018 at 19:04, Dan Ravensloft <dan.ravensloft at gmail.com>
> wrote:
>
>> On Sat, 8 Sep 2018 at 15:01, Tim Northover <t.p.northover at gmail.com>
>> wrote:
>>
>>> At the moment I'm really quite confused about where that PseudoCVT_S_L
>>> is coming from though, the pattern generating it ought to be disabled.
>>
>> I commented out that pattern and Clang now complains about not being able
>> to select a valid instruction, but it doesn't segfault, suggesting that
>> pattern is definitely causing the crash.
>>
> I suppose I'll need to familiarise myself with the Clang pattern syntax
> anyway, because of the various major inconsistencies of the R5900 (it has
> no DMULT(U) or DDIV(U) instructions, which means it's not entirely MIPS III
> compliant).
>
> In other news, the "unexpected illegal type" assert is now fixed in trunk,
> which is the first step in a long, long path to bringing up support for
> this...*quirky*...architecture.
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180916/7a9941c3/attachment.html>