Binutils and GDB are kept in the same repository but follow seperate
relaese streams. We've been release GDB versions based on binutils
tags, but this is the wrong thing to do and has caused multiple
headaches related to our out-of-tree GDB port.
This patch splits the binutils and GDB submodules, but doesn't actually
change the versions.
expat is required by cross for OpenOCD support, but not provided for native
builds, so replace BINUTILS_GDB_TARGET_FLAGS with BINUTILS_GDB_NATIVE_FLAGS.
248124ac2e RISC-V: Add missing privileged spec registers.
bee792f83a RISC-V: Add compressed instruction hints, and a few misc cleanups.
7d895b6f4c Add missing RISC-V fsrmi and fsflagsi instructions.
04d33e4a83 Objcopy interleave fails if section address not multiple of interleave.
71a8fbb5aa Really fix riscv shared library __global_pointer$ problem.
355497b4a7 Riscv shared libraries should not export __global_pointer$.
bfd4dc4363 Fix for texinfo 4.8.
caf839a4a4 Update and clean up RISC-V gas documentation.
df726395c9 Give Palmer co-credit for last patch.
0362ab46db Fix riscv malloc error on small alignment after norvc.
3adcc16f76 Merge pull request #126 from riscv/native-gdb
be4ba40749 Make native gdb builds work.
* Makefile.in (relsrcdir): New.
(stamps/build-gcc-linux-stage1, stamps/build-gcc-linux-stage2)
(stamps/build-gcc-newlib-stage1, stamps/build-gcc-newlib/stage2): Pass
--src to configure set from relsrcdir.
This might be an actaul newlib bug: it's not providing a range error
when taking log1p of -1e80, but it appears that this triggered a glibc
bug from a while ago that may have not been fixed in newlib. I'm not
sure why the bug is just manifesting now (the newlib sources haven't
changed for a long time), but the glibc version has some macros that
force the evaluation of particular floating-point expressions (one of
which produces the range error) that don't exist in newlib.
I'm OK whitelisting the error for the next release, despite it
technically being a regression. log1p isn't a standard function, and I
doubt embedded users are going to notice. That said, we should still
fix it.