From: Andrew Pinski <pinskia@gmail.com>
To: "Michał Dec" <moog621@gmail.com>
Cc: "<newlib@sourceware.org>" <newlib@sourceware.org>
Subject: Re: newlib is broken for spu target since 2.5.0.20170623
Date: Sat, 11 Jul 2020 17:42:44 -0700 [thread overview]
Message-ID: <CA+=Sn1muEii7BKiP+sC_zSjW9ZAdiyqstWNJX3CGKz4az7YHsg@mail.gmail.com> (raw)
In-Reply-To: <1bee626a-c669-ff0a-8bf6-803670ea9e81@gmail.com>
On Sat, Jul 11, 2020 at 4:57 PM Michał Dec via Newlib
<newlib@sourceware.org> wrote:
>
> Hello,
>
> I wanted to make a crosscompiler for the SPU on my PS3 with the newest
> newlib 3.3.0 but it failed. I've reported this issue to my distribution
> here https://bugs.gentoo.org/732206 and my investigations turned out
> this has been broken for some time now. I've also made a diff of the
> last working version and the first broken version here
> https://github.com/grepwood/newlib/commit/831b6666af1f83ac173b491a5c191246203ddc37
> and I can see there's something wrong POSIX threads but I'm not entirely
> sure. Could anyone assist please? I know the SPU target is pretty much
> dead, but there are also plans to bring the open-source PS3 SDK PSL1GHT
> up to speed with new networking code from newlib, and they will also be
> blocked if they can't get a compiler for the SPU.
Well the SPU back-end for GCC was removed in GCC 10.x and gdb release
this year. So I am thinking we should remove support for spu from the
newlib too. I am shocked it was removed from binutils though.
Thanks,
Andrew Pinski
>
> Best regards,
>
> Michał Dec
>
next prev parent reply other threads:[~2020-07-12 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 23:54 Michał Dec
2020-07-12 0:42 ` Andrew Pinski [this message]
2020-07-12 9:58 ` Michał Dec
2020-07-12 10:50 ` Andrew Pinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+=Sn1muEii7BKiP+sC_zSjW9ZAdiyqstWNJX3CGKz4az7YHsg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=moog621@gmail.com \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).