Re: [PATCH v1 1/7] LoongArch Port: gcc

On Tue, 2021-11-09 at 23:52 +0800, Xi Ruoyao via Gcc-patches wrote: > > gcc trunk does not build with glibc-2.34+ and --enable-werror-always > > :( > > > > I've sent the fix as > > https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583820.html. > > I applied the 7 patches and my fix onto

Re: [PATCH v1 1/7] LoongArch Port: gcc

On Tue, 2021-11-09 at 21:53 +0800, Xi Ruoyao via Gcc-patches wrote: > On Mon, 2021-11-08 at 23:14 +, Joseph Myers wrote: > > /* snip */ > > > Please make sure the back end builds cleanly with current GCC mainline.  > > This can be tested either with a native bootstrap, or by building a

Re: [PATCH v1 1/7] LoongArch Port: gcc

On Mon, 2021-11-08 at 23:14 +, Joseph Myers wrote: /* snip */ > Please make sure the back end builds cleanly with current GCC mainline.  > This can be tested either with a native bootstrap, or by building a cross > compiler, using a native compiler of the same GCC mainline version for the

Re: [PATCH v1 1/7] LoongArch Port: gcc

You have: > +#define GLIBC_DYNAMIC_LINKER_LP64 "/lib64/ld.so.1" See my comments on the glibc patch series . Specifically, the point that all new glibc ports should have unique per-ABI dynamic linker names for each ABI

Re: [PATCH v1 1/7] LoongArch Port: gcc

On Mon, 2021-11-08 at 10:30 +0800, Chenghua Xu wrote: > This patch does not arrive at  mail list. Send as an attachment in a > compressed format. I think .patch.gz is perferred instead of .tar.gz. And is it possible to seperate this into multiple commits? For example the whole "-march=native"

Re: [PATCH v1 1/7] LoongArch Port: gcc

This patch does not arrive at  mail list. Send as an attachment in a compressed format. v1-0001-LoongArch-Port-gcc.patch.tar.xz Description: application/xz