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/111367] Error: operand out of range (0x1391c is not between 0xffffffffffff8000 and 0x7fff)
Date: Mon, 23 Oct 2023 05:38:32 +0000	[thread overview]
Message-ID: <bug-111367-4-3qV3dBSOYs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111367-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:3ae7f45ea0d9caa54ebd5dc19caf94fa002e7ee2

commit r13-7975-g3ae7f45ea0d9caa54ebd5dc19caf94fa002e7ee2
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Thu Oct 12 00:05:03 2023 -0500

    rs6000: Make 32 bit stack_protect support prefixed insn [PR111367]

    As PR111367 shows, with prefixed insn supported, some of
    checkings consider it's able to leverage prefixed insn
    for stack protect related load/store, but since we don't
    actually change the emitted assembly for 32 bit, it can
    cause the assembler error as exposed.

    Mike's commit r10-4547-gce6a6c007e5a98 has already handled
    the 64 bit case (DImode), this patch is to treat the 32
    bit case (SImode) by making use of mode iterator P and
    ptrload attribute iterator, also fixes the constraints
    to match the emitted operand formats.

            PR target/111367

    gcc/ChangeLog:

            * config/rs6000/rs6000.md (stack_protect_setsi): Support prefixed
            instruction emission and incorporate to stack_protect_set<mode>.
            (stack_protect_setdi): Rename to ...
            (stack_protect_set<mode>): ... this, adjust constraint.
            (stack_protect_testsi): Support prefixed instruction emission and
            incorporate to stack_protect_test<mode>.
            (stack_protect_testdi): Rename to ...
            (stack_protect_test<mode>): ... this, adjust constraint.

    gcc/testsuite/ChangeLog:

            * g++.target/powerpc/pr111367.C: New test.

    (cherry picked from commit 530babc2058be5f2b06b1541384e7b730c368b93)

  parent reply	other threads:[~2023-10-23  5:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 10:01 [Bug target/111367] New: " malat at debian dot org
2023-09-11 10:02 ` [Bug target/111367] " malat at debian dot org
2023-09-11 10:02 ` malat at debian dot org
2023-09-11 10:03 ` malat at debian dot org
2023-09-12  9:35 ` linkw at gcc dot gnu.org
2023-09-15  7:44 ` linkw at gcc dot gnu.org
2023-09-18  2:39 ` linkw at gcc dot gnu.org
2023-09-18  2:42 ` linkw at gcc dot gnu.org
2023-09-18 17:03 ` bergner at gcc dot gnu.org
2023-09-18 17:56 ` segher at gcc dot gnu.org
2023-09-19  2:15 ` linkw at gcc dot gnu.org
2023-09-19 15:19 ` segher at gcc dot gnu.org
2023-09-19 16:31 ` gnu@the-meissners.org
2023-09-21  6:57 ` linkw at gcc dot gnu.org
2023-10-12  5:06 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:32 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:35 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:38 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-23  6:22 ` linkw 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-111367-4-3qV3dBSOYs@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).