Re: [OpenRISC] Removing architectures without upstream gcc support

2018-02-26 Thread whitequark
On 2018-02-26 12:10, Philipp Wagner wrote: Actually the LLVM port of or1k isn't upstream either. CCing whitequark, who might know more about the (non-)plans of getting the backend upstream. I also don't know of anyone having tried to build the openrisc kernel with LLVM, would certainly be an inte

Re: [OpenRISC] Removing architectures without upstream gcc support

2018-02-26 Thread Philipp Wagner
On 02/26/2018 09:00 AM, Arnd Bergmann wrote: On Sun, Feb 25, 2018 at 4:43 PM, Philipp Wagner wrote: Am 22.02.2018 um 16:45 schrieb Arnd Bergmann: While building the cross-toolchains, I noticed that overall, we can build almost all linux target architectures with upstream binutils and gcc these

Re: [OpenRISC] Removing architectures without upstream gcc support

2018-02-26 Thread Arnd Bergmann
On Sun, Feb 25, 2018 at 4:43 PM, Philipp Wagner wrote: > Am 22.02.2018 um 16:45 schrieb Arnd Bergmann: >> While building the cross-toolchains, I noticed that overall, we can build >> almost >> all linux target architectures with upstream binutils and gcc these days, >> however there are still som

Re: [OpenRISC] Removing architectures without upstream gcc support

2018-02-25 Thread Richard Henderson
On 02/23/2018 10:19 AM, Al Viro wrote: > For m68k, > IIRC, qemu is mostly for coldfire and friends with aranym > working for m68k/MMU testing. Laurent Vivier is in the process of fixing that upstream, it won't all make qemu 2.12. He has a branch with full support for a Mac Quadra 800: https://

Re: [OpenRISC] Removing architectures without upstream gcc support

2018-02-25 Thread Philipp Wagner
Am 22.02.2018 um 16:45 schrieb Arnd Bergmann: > While building the cross-toolchains, I noticed that overall, we can build > almost > all linux target architectures with upstream binutils and gcc these days, > however there are still some exceptions, and I'd like to find out if anyone > has objecti