On 05/07/18 18:51, Palmer Dabbelt wrote:
I'm not sure what the policy is on getting config stuff approved for
commit, but just FYI there's another RISC-V related patch to
config.sub that changes the behavior of "riscv-*" tuples. I'm
assuming we should take both, as it's odd to sync half way
On 07/05/2018 09:18 PM, Jim Wilson wrote:
> On Thu, Jul 5, 2018 at 12:22 PM, Liviu Ionescu wrote:
>>> On 5 Jul 2018, at 22:17, Jim Wilson wrote:
>>> ... I can fix the gcc config.sub to make it work.
>> Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`.
>
> I added patches
On Thu, Jul 5, 2018 at 12:22 PM, Liviu Ionescu wrote:
>> On 5 Jul 2018, at 22:17, Jim Wilson wrote:
>> ... I can fix the gcc config.sub to make it work.
> Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`.
I added patches to binutils and gcc to make riscv-elf work.
riscv-r
> On 5 Jul 2018, at 22:17, Jim Wilson wrote:
>
> ... I can fix the gcc config.sub to make it work.
Or you can edit `gcc/config.gcc` and trigger an error for `riscv-linux*`.
Regards,
Liviu
On Thu, Jul 5, 2018 at 11:31 AM, Liviu Ionescu wrote:
> If this is really a problem I guess you can blacklist it somehow.
> But this proves once again that Linux native compilers and cross embedded
> toolchains should be processed differently.
It isn't a major problem. There is the issue that t
> On 5 Jul 2018, at 21:26, Jim Wilson wrote:
>
> because it adds riscv-linux as a valid configure tuple, and we never wanted
> that
If this is really a problem I guess you can blacklist it somehow.
But this proves once again that Linux native compilers and cross embedded
toolchains should
On 07/05/2018 09:51 AM, Palmer Dabbelt wrote:
When I try to build it I see "Unsupported RISC-V target
riscv-unknown-elf", so there's at least some extra autoconf wizadry that
needs to happen in here. I'm actually not sure what the "riscv-*"
tuples are supposed to do so I've added Liviu as I do
> On 5 Jul 2018, at 19:51, Palmer Dabbelt wrote:
>
> ... When I try to build it I see "Unsupported RISC-V target
> riscv-unknown-elf",
I guess configure is fine, you need to allow for the `riscv-` prefix in
gcc/config.gcc, around line 3982
> so there's at least some extra autoconf wizadry
On 07/05/2018 10:51 AM, Palmer Dabbelt wrote:
> On Thu, 05 Jul 2018 05:00:20 PDT (-0700),
> sebastian.hu...@embedded-brains.de wrote:
>> * config.guess: Sync with upstream version 2018-06-26.
>> * config.sub: Sync with upstream version 2018-07-02.
>> ---
>> config.guess | 6 +++---
>> conf
On 07/05/2018 06:00 AM, Sebastian Huber wrote:
> * config.guess: Sync with upstream version 2018-06-26.
> * config.sub: Sync with upstream version 2018-07-02.
OK. And I think in general syncing to the latest version from upstream
ought not require explicit approval.
Richi/Jakub have t
On Thu, 05 Jul 2018 05:00:20 PDT (-0700), sebastian.hu...@embedded-brains.de
wrote:
* config.guess: Sync with upstream version 2018-06-26.
* config.sub: Sync with upstream version 2018-07-02.
---
config.guess | 6 +++---
config.sub | 8 +++-
2 files changed, 10 insertions(
On 05/07/18 14:00, Sebastian Huber wrote:
* config.guess: Sync with upstream version 2018-06-26.
* config.sub: Sync with upstream version 2018-07-02.
I would like to back port this also to GCC 8.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchhei
* config.guess: Sync with upstream version 2018-06-26.
* config.sub: Sync with upstream version 2018-07-02.
---
config.guess | 6 +++---
config.sub | 8 +++-
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/config.guess b/config.guess
index 883a6713bf0..445c406
13 matches
Mail list logo
