Re: HELP: MIPS PC Relative Addressing

2021-02-27 Thread Maciej W. Rozycki
On Thu, 25 Feb 2021, Jiaxun Yang wrote: > > You may want to use composed relocations to refer to .LA1 (R_MIPS_32) and > > .LA0 (R_MIPS_SUB). There may or may not be linker updates needed; unlike > > the RISC-V one the MIPS BFD backend already supports composed relocations > > with the usual ELF

gcc-10-20210227 is now available

2021-02-27 Thread GCC Administrator via Gcc
Snapshot gcc-10-20210227 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20210227/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

boostrap failure with newlib

2021-02-27 Thread sotrdg sotrdg via Gcc
../../../gcc/libssp/ssp.c: In function '__guard_setup': ../../../gcc/libssp/memcpy-chk.c:45:15: error: unknown type name 'size_t' 45 | size_t len, size_t slen) | ^~ ../../../gcc/libssp/ssp.c:93:12: warning: implicit declaration of function 'open' [-Wimplici

Re: GCC generates non-compliant MIPS relocation data? Obscure GNU extension?

2021-02-27 Thread Maciej W. Rozycki
On Fri, 19 Feb 2021, Maciej W. Rozycki wrote: > It looks to me however that you actually have control over the relocation > processing code you have referred, so how about improving it to handle the > GNU R_MIPS_HI16 extension as well? FWIW note that the extension has been around for ~25 year