Re: Welcome to the list!

[Karsten Merker <merker@debian.org>]

On Wed, Nov 09, 2016 at 03:21:43PM +0100, Karsten Merker wrote:

> - The RISC-V binutils codebase is in principle upstreamed since a
>   few days:
> 
>   https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=e23eba971dd409b999dd83d8df0f842680c1c642
> 
>   Nonetheless there are AFAIK still a number of points that need
>   adjustments and may break compatibility with (some) existing
>   binaries.  AFAIK one thing that is still being discussed is the
>   correct format/value of certain ELF header data for RISC-V, but
>   I am not familiar with the specifics of ELF, so I don't know
>   any details.

I have in the meantime done a bit of further research regarding
the ELF header changes.  The issue concerns the bits in the ELF
header which specify the floating point ABI that is used by the
code in the ELF file.  This in turn is a result of a change in
the floating point ABI as described at

https://github.com/riscv/riscv-gnu-toolchain/issues/187#issuecomment-255650071

resulting in the following commit:

https://github.com/riscv/riscv-gnu-toolchain/commit/a1e7a925c16f8ff34c5a6d794bfe9b9d5660268f

For further information please also cf. the thread "Some RISC-V
Post-Merge Cleanup" on the upstream binutils list at
https://sourceware.org/ml/binutils/2016-11/msg00011.html.

> - I currently don't know the exact state for glibc.

According to

https://groups.google.com/a/groups.riscv.org/forum/#!msg/sw-dev/8FXtqRz_RS8/6GgcTZCQIgAJ

there seems to also have been an unrelated change in glibc that
could cause compatibility issues with older binaries.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.