bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/23451] RISC-V gas aborts with "Error: unknown default architect


From: wilson at gcc dot gnu.org
Subject: [Bug gas/23451] RISC-V gas aborts with "Error: unknown default architecture `'" in GCC configure tests
Date: Fri, 27 Jul 2018 15:56:21 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=23451

Jim Wilson <wilson at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2018-07-27
           Assignee|unassigned at sourceware dot org   |wilson at gcc dot 
gnu.org
     Ever confirmed|0                           |1

--- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> ---
I did a build test, but I see now that it builds but doesn't run.  Annoying,
but this is easy to fix.

I regularly test riscv32-* and riscv64-* as these are the officially supported
targets, but I'm not interested in testing riscv-*.  Use riscv-* at your own
risk.

We got in the current situation because of two main reasons.
1) There is a person (not Sebastian) willing to annoy people until he gets what
he wants, and has spent so much time annoying so many people to get riscv-*
that at least one key person has given up trying to fight him.
2) Both Sebatian and Ben Ellison were on vacation at the same time right before
the last binutils release, limiting my options for late configure related fixes
before the release.

I don't like making non-backward compatible changes.  Also, if we remove it, we
have to start fighting a certain person again.  I'm willing to do that, but it
will be hard now that some people have given up the fight.  So I think we are
stuck with riscv-* for now.  I won't be testing it, but I will fix bugs when
they are reported against it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]