On Mon, 2021-12-20 at 15:35 +0800, Xi Ruoyao via Gcc-patches wrote:
> Hi,
>
> I've bootstraped the patch with my GNU-stack fix
> (https://github.com/loongson/gcc/pull/62) and --enable-werror-always.
> Bootstrap succeeded, but with some warnings:
>
> ../../gcc/config/loongarch/loongarch.md:3205:1
Hi,
I've bootstraped the patch with my GNU-stack fix
(https://github.com/loongson/gcc/pull/62) and --enable-werror-always.
Bootstrap succeeded, but with some warnings:
../../gcc/config/loongarch/loongarch.md:3205:1: warning: operand 0 missing mode?
../../gcc/config/loongarch/loongarch.md:3282:1:
Hi Ruoyao,
Thank you for your attention.
> GCC 12 development cycle is at stage 3 (general bugfixing) now. So a
> new port have to wait until stage 1 of GCC 13 begins (in mid 2022, I
> guess).
I know it is stage3, but we are a new target, it's ok for GCC 12.
On Fri, 2021-12-17 at 15:45 +0800, Paul Hua via Gcc-patches wrote:
> Hi Joseph,
>
> Thanks for your suggestion, Those macros can be removed, we will send
> the v4 version soon.
>
> Are there any problems in this series of patches?
I'm not a compiler expert, but I'll bootstrap it once my 5th Linu
Hi Joseph,
Thanks for your suggestion, Those macros can be removed, we will send
the v4 version soon.
Are there any problems in this series of patches?
In other words, What conditions are required for LoongArch back-end merged?
By the way, We are preparing the LoongArch machine to send to Cfarm
On Fri, 10 Dec 2021, Chenghua Xu wrote:
> + /* Macros dependent on the C dialect. */
> + if (preprocessing_asm_p ())
> +{
> + builtin_define_std ("LANGUAGE_ASSEMBLY");
> + builtin_define ("_LANGUAGE_ASSEMBLY");
> +}
> + else if (c_dialect_cxx ())
> +{
> + builtin_def
From: chenglulu
gcc/
*config/loongarch/loongarch-c.c
---
gcc/config/loongarch/loongarch-c.c | 136 +
1 file changed, 136 insertions(+)
create mode 100644 gcc/config/loongarch/loongarch-c.c
diff --git a/gcc/config/loongarch/loongarch-c.c
b/gcc/config/loonga
