Re: [PATCH v8 00/12] Add LoongArch support.
> > And based on the history of RISC-V port > > (https://gcc.gnu.org/pipermail/gcc/2017-January/222595.html) the process > > for a new port seems: > > > > 1. Get a permission from the Steering Committee. > > 2. Add one or two port maintainers into MAINTAINERS file. > > 3. Now the technical reviewing of the patch series just begin. > > > > Hi Ruoyao, > Thanks for your advice. But I don't know how to contact the GCC > Steering Committee. > > Hi David, > Any suggestions? Sorry, CCed David Edelsohn.
Re: [PATCH v8 00/12] Add LoongArch support.
> > And based on the history of RISC-V port > (https://gcc.gnu.org/pipermail/gcc/2017-January/222595.html) the process > for a new port seems: > > 1. Get a permission from the Steering Committee. > 2. Add one or two port maintainers into MAINTAINERS file. > 3. Now the technical reviewing of the patch series just begin. > Hi Ruoyao, Thanks for your advice. But I don't know how to contact the GCC Steering Committee. Hi David, Any suggestions?
Re: [PATCH v6 11/12] LoongArch Port: gcc/testsuite
Hi Mike, Thanks for your review. On Wed, Feb 16, 2022 at 12:30 PM Mike Stump via Gcc-patches wrote: > > On Jan 28, 2022, at 5:49 AM, chenglulu wrote: > > > > gcc/testsuite/ > > > >* g++.dg/cpp0x/constexpr-rom.C: Add build options for LoongArch. > >* g++.old-deja/g++.abi/ptrmem.C: Add LoongArch support. > >* g++.old-deja/g++.pt/ptrmem6.C: xfail for LoongArch. > >* gcc.dg/20020312-2.c: Add LoongArch support. > >* gcc.dg/loop-8.c: Skip on LoongArch. > >* gcc.dg/torture/stackalign/builtin-apply-2.c: Likewise. > >* gcc.dg/tree-ssa/ssa-fre-3.c: Likewise. > >* go.test/go-test.exp: Define the LoongArch target. > >* lib/target-supports.exp: Like wise. > >* gcc.target/loongarch/loongarch.exp: New file. > >* gcc.target/loongarch/tst-asm-const.c: Like wise. > > Ok.
Ping ?: [PATCH v7 00/12] Add LoongArch support.
ping? On Sat, Feb 12, 2022 at 11:12 AM wrote: > > From: Chenghua Xu > > Hi, all: > > This is the v7 version of LoongArch Port. Please review. > > We know it is stage4, I think it is ok for a new prot. > The kernel side upstream waiting for a approval by gcc side, > if it is blocked by stage4, a approval for GCC13 will be appreciation. > > > The LoongArch architecture (LoongArch) is an Instruction Set > Architecture (ISA) that has a Reduced Instruction Set Computer (RISC) > style. > The documents are on > https://loongson.github.io/LoongArch-Documentation/README-EN.html > > The ELF ABI Documents are on: > https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html > > The binutils has been merged into trunk: > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=560b3fe208255ae909b4b1c88ba9c28b09043307 > > Note: We split -mabi= into -mabi=lp64d/f/s, the new options not support by > upstream binutils yet, > this GCC port requires the following patch applied to binutils to build. > https://github.com/loongson/binutils-gdb/commit/aacb0bf860f02aa5a7dcb76dd0e392bf871c7586 > (will be submitted to upstream after gcc side comfirmed) > > We have compiled more than 300 CLFS packages with this compiler. > The CLFS are currently used on Cfarm machines gcc400 and gcc401. > > Changelog: > > v1 -> v2 > 1. Split patch set. > 2. Change some code style. > 3. Add -mabi=lp64d/f/s options. > 4. Change GLIBC_DYNAMIC_LINKER_LP64 name. > > v2 -> v3 > 1. Change some code style. > 2. Bug fix. > > v3 -> v4 > 1. Change some code style. > 2. Bug fix. > 3. Delete some builtin macros. > > v4 -> v5 > 1. delete wrong insn zero_extendsidi2_internal. > 2. Adjust some build options. > 3. Change some .c files to .cc. > > v5 -> v6 > 1. Fix compilation issues. The generated files *.opt and *.h >are generated to $(objdir). > > v6 -> v7 > 1. Bug fix. > 2. Change some code style. > > chenglulu (12): > LoongArch Port: Regenerate configure > LoongArch Port: gcc build > LoongArch Port: Regenerate gcc/configure. > LoongArch Port: Machine description files. > LoongArch Port: Machine description C files and .h files. > LoongArch Port: Builtin functions. > LoongArch Port: Builtin macros. > LoongArch Port: libgcc > LoongArch Port: Regenerate libgcc/configure. > LoongArch Port: libgomp > LoongArch Port: gcc/testsuite > LoongArch Port: Add doc. > > config/picflag.m4 |3 + > configure | 10 +- > configure.ac | 10 +- > contrib/config-list.mk|5 +- > contrib/gcc_update|2 + > .../config/loongarch/loongarch-common.cc | 73 + > gcc/config.gcc| 410 +- > gcc/config/host-linux.cc |2 + > gcc/config/loongarch/constraints.md | 212 + > gcc/config/loongarch/generic.md | 132 + > gcc/config/loongarch/genopts/genstr.sh| 91 + > .../loongarch/genopts/loongarch-strings | 58 + > gcc/config/loongarch/genopts/loongarch.opt.in | 189 + > gcc/config/loongarch/gnu-user.h | 84 + > gcc/config/loongarch/la464.md | 132 + > gcc/config/loongarch/larchintrin.h| 413 ++ > gcc/config/loongarch/linux.h | 50 + > gcc/config/loongarch/loongarch-builtins.cc| 511 ++ > gcc/config/loongarch/loongarch-c.cc | 109 + > gcc/config/loongarch/loongarch-cpu.cc | 206 + > gcc/config/loongarch/loongarch-cpu.h | 30 + > gcc/config/loongarch/loongarch-def.c | 164 + > gcc/config/loongarch/loongarch-def.h | 151 + > gcc/config/loongarch/loongarch-driver.cc | 187 + > gcc/config/loongarch/loongarch-driver.h | 69 + > gcc/config/loongarch/loongarch-ftypes.def | 106 + > gcc/config/loongarch/loongarch-modes.def | 29 + > gcc/config/loongarch/loongarch-opts.cc| 580 ++ > gcc/config/loongarch/loongarch-opts.h | 86 + > gcc/config/loongarch/loongarch-protos.h | 241 + > gcc/config/loongarch/loongarch-str.h | 57 + > gcc/config/loongarch/loongarch-tune.h | 72 + > gcc/config/loongarch/loongarch.cc | 6318 + > gcc/config/loongarch/loongarch.h | 1271 > gcc/config/loongarch/loongarch.md | 3702 ++ > gcc/config/loongarch/loongarch.opt| 189 + > gcc/config/loongarch/predicates.md| 531 ++ > gcc/config/loongarch/sync.md | 574 ++ > gcc/config/loongarch/t-linux | 53 + > gcc/config/loongarch/t-loongarch | 68 + > gcc/configure | 66 +- > gcc/configure.ac | 33 +- > gcc/doc/install.texi | 47 +- > gcc/doc/invoke.texi | 201 + >
Ping for [PATCH v6 00/12] Add LoongArch support.
ping ? On Fri, Jan 28, 2022 at 9:50 PM chenglulu wrote: > > The LoongArch architecture (LoongArch) is an Instruction Set > Architecture (ISA) that has a Reduced Instruction Set Computer (RISC) > style. > The documents are on > https://loongson.github.io/LoongArch-Documentation/README-EN.html > > The ELF ABI Documents are on: > https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html > > The binutils has been merged into trunk: > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=560b3fe208255ae909b4b1c88ba9c28b09043307 > > Note: We split -mabi= into -mabi=lp64d/f/s, the new options not support by > upstream binutils yet, > this GCC port requires the following patch applied to binutils to build. > https://github.com/loongson/binutils-gdb/commit/aacb0bf860f02aa5a7dcb76dd0e392bf871c7586 > (will be submitted to upstream after gcc side comfirmed) > > We have compiled more than 300 CLFS packages with this compiler. > The CLFS are currently used on Cfarm machines gcc400 and gcc401. > > > changelog: > > v1 -> v2 > 1. Split patch set. > 2. Change some code style. > 3. Add -mabi=lp64d/f/s options. > 4. Change GLIBC_DYNAMIC_LINKER_LP64 name. > > v2 -> v3 > 1. Change some code style. > 2. Bug fix. > > v3 -> v4 > 1. Change some code style. > 2. Bug fix. > 3. Delete some builtin macros. > > v4 -> v5 > 1. delete wrong insn zero_extendsidi2_internal. > 2. Adjust some build options. > 3. Change some .c files to .cc. > > v5 -> v6 > 1. Fix compilation issues. The generated files *.opt and *.h >are generated to $(objdir). > > > chenglulu (12): > LoongArch Port: Regenerate configure > LoongArch Port: gcc build > LoongArch Port: Regenerate gcc/configure. > LoongArch Port: Machine Decsription files. > LoongArch Port: Machine description C files and .h files. > LoongArch Port: Builtin functions. > LoongArch Port: Builtin macros. > LoongArch Port: libgcc > LoongArch Port: Regenerate libgcc/configure. > LoongArch Port: libgomp > LoongArch Port: gcc/testsuite > LoongArch Port: Add doc. > > config/picflag.m4 |3 + > configure | 10 +- > configure.ac | 10 +- > contrib/config-list.mk|5 +- > contrib/gcc_update|2 + > .../config/loongarch/loongarch-common.cc | 73 + > gcc/config.gcc| 410 +- > gcc/config/host-linux.cc |2 + > gcc/config/loongarch/constraints.md | 212 + > gcc/config/loongarch/generic.md | 132 + > gcc/config/loongarch/genopts/genstr.sh| 91 + > .../loongarch/genopts/loongarch-strings | 58 + > gcc/config/loongarch/genopts/loongarch.opt.in | 189 + > gcc/config/loongarch/gnu-user.h | 84 + > gcc/config/loongarch/la464.md | 132 + > gcc/config/loongarch/larchintrin.h| 413 ++ > gcc/config/loongarch/linux.h | 50 + > gcc/config/loongarch/loongarch-builtins.cc| 511 ++ > gcc/config/loongarch/loongarch-c.cc | 109 + > gcc/config/loongarch/loongarch-cpu.cc | 206 + > gcc/config/loongarch/loongarch-cpu.h | 30 + > gcc/config/loongarch/loongarch-def.c | 164 + > gcc/config/loongarch/loongarch-def.h | 151 + > gcc/config/loongarch/loongarch-driver.cc | 187 + > gcc/config/loongarch/loongarch-driver.h | 69 + > gcc/config/loongarch/loongarch-ftypes.def | 106 + > gcc/config/loongarch/loongarch-modes.def | 29 + > gcc/config/loongarch/loongarch-opts.cc| 580 ++ > gcc/config/loongarch/loongarch-opts.h | 86 + > gcc/config/loongarch/loongarch-protos.h | 241 + > gcc/config/loongarch/loongarch-str.h | 57 + > gcc/config/loongarch/loongarch-tune.h | 72 + > gcc/config/loongarch/loongarch.cc | 6330 + > gcc/config/loongarch/loongarch.h | 1271 > gcc/config/loongarch/loongarch.md | 3702 ++ > gcc/config/loongarch/loongarch.opt| 189 + > gcc/config/loongarch/predicates.md| 553 ++ > gcc/config/loongarch/sync.md | 574 ++ > gcc/config/loongarch/t-linux | 53 + > gcc/config/loongarch/t-loongarch | 68 + > gcc/configure | 66 +- > gcc/configure.ac | 33 +- > gcc/doc/install.texi | 47 +- > gcc/doc/invoke.texi | 201 + > gcc/doc/md.texi | 55 + > gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C|2 +- > gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C |2 +- > gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C |2 +- > gcc/testsuite/gcc.dg/20020312-2.c |2 + > gcc/testsuite/gcc.dg/loop-8.c |2 +-
Re: [PATCH v4 00/12] Add LoongArch support.
Hi all, Ping? By the way, the LoongArch machine is already connected to the Cfarm and will be announced soon. You can login through ssh. ssh -l your-cfarm-user-name -p 25469 114.242.206.180 On Fri, Dec 24, 2021 at 5:28 PM chenglulu wrote: > > The LoongArch architecture (LoongArch) is an Instruction Set > Architecture (ISA) that has a Reduced Instruction Set Computer (RISC) > style. > The documents are on > https://loongson.github.io/LoongArch-Documentation/README-EN.html > > The ELF ABI Documents are on: > https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html > > The binutils has been merged into trunk: > https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=560b3fe208255ae909b4b1c88ba9c28b09043307 > > Note: We split -mabi= into -mabi=lp64d/f/s, the new options not support by > upstream binutils yet, > this GCC port requires the following patch applied to binutils to build. > https://github.com/loongson/binutils-gdb/commit/aacb0bf860f02aa5a7dcb76dd0e392bf871c7586 > (will be submitted to upstream after gcc side comfirmed) > > > changelog: > > v1 -> v2 > 1. Split patch set. > 2. Change some code style. > 3. Add -mabi=lp64d/f/s options. > 4. Change GLIBC_DYNAMIC_LINKER_LP64 name. > > v2 -> v3 > 1. Change some code style. > 2. Bug fix. > > v3 -> v4 > 1. Change some code style. > 2. Bug fix. > 3. Delete some builtin macros. > > Add LoongArch support. > > chenglulu (12): > LoongArch Port: Regenerate configure > LoongArch Port: gcc build > LoongArch Port: Regenerate gcc/configure. > LoongArch Port: Machine Decsription files. > LoongArch Port: Machine description C files and .h files. > LoongArch Port: Builtin functions. > LoongArch Port: Builtin macros. > LoongArch Port: libgcc > LoongArch Port: Regenerate libgcc/configure. > LoongArch Port: libgomp > LoongArch Port: gcc/testsuite > LoongArch Port: Add doc. > > config/picflag.m4 |3 + > configure | 10 +- > configure.ac | 10 +- > contrib/config-list.mk|5 +- > .../config/loongarch/loongarch-common.c | 63 + > gcc/config.gcc| 400 +- > gcc/config/host-linux.c |2 + > gcc/config/loongarch/constraints.md | 212 + > gcc/config/loongarch/generic.md | 132 + > gcc/config/loongarch/genopts/genstr.sh| 91 + > .../loongarch/genopts/loongarch-strings | 58 + > gcc/config/loongarch/genopts/loongarch.opt.in | 189 + > gcc/config/loongarch/gnu-user.h | 78 + > gcc/config/loongarch/la464.md | 132 + > gcc/config/loongarch/larchintrin.h| 413 ++ > gcc/config/loongarch/linux.h | 50 + > gcc/config/loongarch/loongarch-builtins.c | 511 ++ > gcc/config/loongarch/loongarch-c.c| 111 + > gcc/config/loongarch/loongarch-cpu.c | 206 + > gcc/config/loongarch/loongarch-cpu.h | 30 + > gcc/config/loongarch/loongarch-def.c | 164 + > gcc/config/loongarch/loongarch-def.h | 151 + > gcc/config/loongarch/loongarch-driver.c | 187 + > gcc/config/loongarch/loongarch-driver.h | 69 + > gcc/config/loongarch/loongarch-ftypes.def | 106 + > gcc/config/loongarch/loongarch-modes.def | 29 + > gcc/config/loongarch/loongarch-opts.c | 582 ++ > gcc/config/loongarch/loongarch-opts.h | 86 + > gcc/config/loongarch/loongarch-protos.h | 242 + > gcc/config/loongarch/loongarch-str.h | 57 + > gcc/config/loongarch/loongarch-tune.h | 72 + > gcc/config/loongarch/loongarch.c | 6461 + > gcc/config/loongarch/loongarch.h | 1291 > gcc/config/loongarch/loongarch.md | 3829 ++ > gcc/config/loongarch/loongarch.opt| 189 + > gcc/config/loongarch/predicates.md| 553 ++ > gcc/config/loongarch/sync.md | 574 ++ > gcc/config/loongarch/t-linux | 53 + > gcc/config/loongarch/t-loongarch | 59 + > gcc/configure | 85 +- > gcc/configure.ac | 33 +- > gcc/doc/install.texi | 47 +- > gcc/doc/invoke.texi | 201 + > gcc/doc/md.texi | 55 + > gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C|2 +- > gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C |2 +- > gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C |2 +- > gcc/testsuite/gcc.dg/20020312-2.c |2 + > gcc/testsuite/gcc.dg/loop-8.c |2 +- > .../torture/stackalign/builtin-apply-2.c |2 +- > gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-3.c |2 +- > .../gcc.target/loongarch/loongarch.exp| 40 + > .../gcc.target/loongarch/tst-asm-const.c
Re: [PATCH v3 06/12] LoongArch Port: Builtin macros.
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.
Re: [PATCH v3 06/12] LoongArch Port: Builtin macros.
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 for testing.
On Tue, Dec 14, 2021 at 8:13 AM Joseph Myers wrote:
>
> 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_define ("_LANGUAGE_C_PLUS_PLUS");
> > + builtin_define ("__LANGUAGE_C_PLUS_PLUS");
> > + builtin_define ("__LANGUAGE_C_PLUS_PLUS__");
> > +}
> > + else
> > +{
> > + builtin_define_std ("LANGUAGE_C");
> > + builtin_define ("_LANGUAGE_C");
> > +}
> > + if (c_dialect_objc ())
> > +{
> > + builtin_define ("_LANGUAGE_OBJECTIVE_C");
> > + builtin_define ("__LANGUAGE_OBJECTIVE_C");
> > + /* Bizarre, but retained for backwards compatibility. */
> > + builtin_define_std ("LANGUAGE_C");
> > + builtin_define ("_LANGUAGE_C");
> > +}
> > +}
>
> I think all of this should be removed. It's a new architecture, there
> should be no need for any such macros for things that are not
> architecture-specific. In general, be careful to remove anything in the
> port that is actually about the peculiarities of what was once done for
> compatibility with existing software for an old architecture (MIPS?) that
> you modelled the port on and that is not considered best practice for a
> new architecture where you can make a fresh start.
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
Re: PING: [PATCH] mips: check MSA support for vector modes [PR100760, PR100761, PR100762]
Looks good to me, but I have no right to approve. On Wed, Jun 30, 2021 at 9:17 PM Xi Ruoyao wrote: > > Ping patch: > https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573213.html > > Status update: bootstrapped with BOOT_CFLAGS="-O3 -mmsa -mloongson-mmi" > (it failed without the patch), and regtested on mips64el-linux-gnu with > no new regression. > > On Sat, 2021-06-19 at 15:34 +0800, Xi Ruoyao wrote: > > Check if the vector mode is really supported by MSA in certain cases, > > instead of testing ISA_HAS_MSA. Simply testing ISA_HAS_MSA can cause > > ICE when MSA is enabled besides other MIPS SIMD extensions (notably, > > Loongson MMI). > > > > Bootstrapped and tested on mips64el-linux-gnu. OK to commit? > > > > gcc/ > > > > * config/mips/mips.c (mips_const_insns): Use > > MSA_SUPPORTED_MODE_P > > instead of ISA_HAS_MSA. > > (mips_expand_vec_unpack): Likewise. > > (mips_expand_vector_init): Likewise. > > > > gcc/testsuite/ > > > > * testsuite/gcc.target/mips/pr100760.c: New test. > > * testsuite/gcc.target/mips/pr100761.c: New test. > > * testsuite/gcc.target/mips/pr100762.c: New test. > -- > Xi Ruoyao >
Re: [PATCH][MIPS] PR target/77510 Reduce size of MIPS core automaton
> > This patch reduce reservation of model do not more than 10 cycles. The > > memory of genautomata down to 1GB. > > How bad is the memory consumption before this change? > almost 2.4GB. see bugzilla comment #4. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77510#c4
Re: [PATCH] MIPS: Fix __builtin_longjmp (PR 64242)
ping? On Sun, Jul 12, 2020 at 2:27 PM Paul Hua wrote: > > From 589dbe8a1c2397bfafefa4e84abe5ec6e6798928 Mon Sep 17 00:00:00 2001 > From: Andrew Pinski > Date: Wed, 12 Feb 2020 11:42:57 + > Subject: [PATCH] MIPS: Fix __builtin_longjmp (PR 64242) > > The problem here is mips has its own builtin_longjmp > pattern and it was not fixed when expand_builtin_longjmp > was fixed. We need to read the new fp and gp before > restoring the stack as the buffer might be a local > variable. > > Change-Id: I3416568e260e6bde3ad5cc470fb4f2ecfa207f05 > Signed-off-by: Andrew Pinski > > This patch from Andrew, I bootstrapped and tested on mips64el-linux-gnu. > > OK for master ? > > gcc/ChangeLog: > > PR middle-end/64242 > * config/mips/mips.md (builtin_longjmp): Restore the frame pointer >and stack pointer and gp.
[PATCH] MIPS: Fix __builtin_longjmp (PR 64242)
>From 589dbe8a1c2397bfafefa4e84abe5ec6e6798928 Mon Sep 17 00:00:00 2001 From: Andrew Pinski Date: Wed, 12 Feb 2020 11:42:57 + Subject: [PATCH] MIPS: Fix __builtin_longjmp (PR 64242) The problem here is mips has its own builtin_longjmp pattern and it was not fixed when expand_builtin_longjmp was fixed. We need to read the new fp and gp before restoring the stack as the buffer might be a local variable. Change-Id: I3416568e260e6bde3ad5cc470fb4f2ecfa207f05 Signed-off-by: Andrew Pinski This patch from Andrew, I bootstrapped and tested on mips64el-linux-gnu. OK for master ? gcc/ChangeLog: PR middle-end/64242 * config/mips/mips.md (builtin_longjmp): Restore the frame pointer and stack pointer and gp. From 589dbe8a1c2397bfafefa4e84abe5ec6e6798928 Mon Sep 17 00:00:00 2001 From: Andrew Pinski Date: Wed, 12 Feb 2020 11:42:57 + Subject: [PATCH] MIPS: Fix __builtin_longjmp (PR 64242) The problem here is mips has its own builtin_longjmp pattern and it was not fixed when expand_builtin_longjmp was fixed. We need to read the new fp and gp before restoring the stack as the buffer might be a local variable. Change-Id: I3416568e260e6bde3ad5cc470fb4f2ecfa207f05 Signed-off-by: Andrew Pinski --- gcc/config/mips/mips.md | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/gcc/config/mips/mips.md b/gcc/config/mips/mips.md index dd9fdd1418d..8bafbe82bd3 100644 --- a/gcc/config/mips/mips.md +++ b/gcc/config/mips/mips.md @@ -6601,9 +6601,19 @@ /* This bit is similar to expand_builtin_longjmp except that it restores $gp as well. */ - mips_emit_move (hard_frame_pointer_rtx, fp); mips_emit_move (pv, lab); + /* Restore the frame pointer and stack pointer and gp. We must use a + temporary since the setjmp buffer may be a local. */ + fp = copy_to_reg (fp); + gpv = copy_to_reg (gpv); emit_stack_restore (SAVE_NONLOCAL, stack); + + /* Ensure the frame pointer move is not optimized. */ + emit_insn (gen_blockage ()); + emit_clobber (hard_frame_pointer_rtx); + emit_clobber (frame_pointer_rtx); + emit_clobber (gp); + mips_emit_move (hard_frame_pointer_rtx, fp); mips_emit_move (gp, gpv); emit_use (hard_frame_pointer_rtx); emit_use (stack_pointer_rtx); -- 2.17.1
