public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [pushed][PR112918][LRA]: Fixing IRA ICE on m68k
Date: Fri, 12 Jan 2024 22:33:12 +0800	[thread overview]
Message-ID: <CAKcpw6UBR_vzzYfK0N77nX_KNJ9ftGfe5hV5S5h-jc-gp3e_Tw@mail.gmail.com> (raw)
In-Reply-To: <937f4ee1-3ed3-6d66-7e19-2bd69a30d6cf@redhat.com>

Vladimir Makarov <vmakarov@redhat.com> 于2024年1月11日周四 22:35写道:
>
> The following patch fixes
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918
>
> The patch was successfully bootstrapped and tested on x86_64, aarch64,
> ppc64le

This patch causes some ICE on MIPS:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113354

PS: how to test cross build for mips:

1. apt install g++-multilib-mipsel-linux-gnu
2. apply patch:
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/641619.html
3. ../configure --target=mipsel-linux-gnu \
      --includedir=/usr/mipsel-linux-gnu/include --enable-multilib \
      --with-arch-32=mips32r2 --with-fp-32=xx \
      --enable-multiarch --enable-targets=all \
      --with-arch-64=mips64r2 --prefix=/usr --disable-libsanitizer
4. make -j

-- 
YunQiang Su

  reply	other threads:[~2024-01-12 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 14:35 Vladimir Makarov
2024-01-12 14:33 ` YunQiang Su [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 22:16 Vladimir Makarov
2023-12-19  0:05 ` Jeff Law
2023-12-19  3:34   ` Jeff Law
2023-12-20 20:35   ` Joseph Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKcpw6UBR_vzzYfK0N77nX_KNJ9ftGfe5hV5S5h-jc-gp3e_Tw@mail.gmail.com \
    --to=wzssyqa@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vmakarov@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).