public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114861] [14/15 Regression] LoongArch: ICE building the kernel with -Os
Date: Sat, 27 Apr 2024 04:00:54 +0000	[thread overview]
Message-ID: <bug-114861-4-3xsFODVjOU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114861-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:

https://gcc.gnu.org/g:140124ad54eef88ca87909f63aedc8aaeacefc65

commit r15-11-g140124ad54eef88ca87909f63aedc8aaeacefc65
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Fri Apr 26 15:59:11 2024 +0800

    LoongArch: Add constraints for bit string operation define_insn_and_split's
[PR114861]

    Without the constrants, the compiler attempts to use a stack slot as the
    target, causing an ICE building the kernel with -Os:

        drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c:3144:1:
        error: could not split insn
        (insn:TI 1764 67 1745
          (set (mem/c:DI (reg/f:DI 3 $r3) [707 %sfp+-80 S8 A64])
               (and:DI (reg/v:DI 28 $r28 [orig:422 raster_config ] [422])
                       (const_int -50331649 [0xfffffffffcffffff])))
          "drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c":1386:21 111
          {*bstrins_di_for_mask}
          (nil))

    Add these constrants to fix the issue.

    gcc/ChangeLog:

            PR target/114861
            * config/loongarch/loongarch.md (bstrins_<mode>_for_mask): Add
            constraints for operands.
            (bstrins_<mode>_for_ior_mask): Likewise.

    gcc/testsuite/ChangeLog:

            PR target/114861
            * gcc.target/loongarch/pr114861.c: New test.

  parent reply	other threads:[~2024-04-27  4:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  7:00 [Bug target/114861] New: LoongArch: Fail to build " xry111 at gcc dot gnu.org
2024-04-26  7:05 ` [Bug target/114861] LoongArch: ICE building " xry111 at gcc dot gnu.org
2024-04-26  7:37 ` xry111 at gcc dot gnu.org
2024-04-26  7:41 ` jakub at gcc dot gnu.org
2024-04-26  7:51 ` xry111 at gcc dot gnu.org
2024-04-26  9:29 ` xry111 at gcc dot gnu.org
2024-04-26 14:27 ` [Bug target/114861] [14/15 Regression] " rguenth at gcc dot gnu.org
2024-04-26 15:57 ` xry111 at gcc dot gnu.org
2024-04-27  4:00 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-27  4:02 ` cvs-commit at gcc dot gnu.org
2024-04-27  4:03 ` xry111 at gcc dot gnu.org

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=bug-114861-4-3xsFODVjOU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).