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/111778] PowerPC constant code change uses an undefined shift
Date: Thu, 12 Oct 2023 20:19:02 +0000	[thread overview]
Message-ID: <bug-111778-4-DH6JoyvTdp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111778-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Michael Meissner <meissner@gcc.gnu.org>:

https://gcc.gnu.org/g:611eef7609f732db65c119a7eab6d50a5fdd5985

commit r14-4600-g611eef7609f732db65c119a7eab6d50a5fdd5985
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Oct 12 16:17:59 2023 -0400

    PR111778, PowerPC: Do not depend on an undefined shift

    I was building a cross compiler to PowerPC on my x86_86 workstation with
the
    latest version of GCC on October 11th.  I could not build the compiler on
the
    x86_64 system as it died in building libgcc.  I looked into it, and I
    discovered the compiler was recursing until it ran out of stack space.  If
I
    build a native compiler with the same sources on a PowerPC system, it
builds
    fine.

    I traced this down to a change made around October 10th:

    | commit 8f1a70a4fbcc6441c70da60d4ef6db1e5635e18a (HEAD)
    | Author: Jiufu Guo <guojiufu@linux.ibm.com>
    | Date:   Tue Jan 10 20:52:33 2023 +0800
    |
    |   rs6000: build constant via li/lis;rldicl/rldicr
    |
    |   If a constant is possible left/right cleaned on a rotated value from
    |   a negative value of "li/lis".  Then, using "li/lis ; rldicl/rldicr"
    |   to build the constant.

    The code was doing a -1 << 64 which is undefined behavior because different
    machines produce different results.  On the x86_64 system, (-1 << 64)
produces
    -1 while on a PowerPC 64-bit system, (-1 << 64) produces 0.  The x86_64
then
    recurses until the stack runs out of space.

    If I apply this patch, the compiler builds fine on both x86_64 as a PowerPC
    crosss compiler and on a native PowerPC system.

    2023-10-12  Michael Meissner  <meissner@linux.ibm.com>

    gcc/

            PR target/111778
            * config/rs6000/rs6000.cc (can_be_built_by_li_lis_and_rldicl):
Protect
            code from shifts that are undefined.
            (can_be_built_by_li_lis_and_rldicr): Likewise.
            (can_be_built_by_li_and_rldic): Protect code from shifts that
            undefined.  Also replace uses of 1ULL with HOST_WIDE_INT_1U.

  parent reply	other threads:[~2023-10-12 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  3:48 [Bug target/111778] New: " meissner at gcc dot gnu.org
2023-10-12  3:50 ` [Bug target/111778] " meissner at gcc dot gnu.org
2023-10-12  4:34 ` pinskia at gcc dot gnu.org
2023-10-12  6:22 ` guojiufu at gcc dot gnu.org
2023-10-12 20:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-13  6:46 ` rguenth at gcc dot gnu.org
2023-10-13 15:03 ` [Bug target/111778] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-13 15:04 ` pinskia 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-111778-4-DH6JoyvTdp@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).