public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work139)] Revert patches Date: Thu, 12 Oct 2023 04:29:57 +0000 (GMT) [thread overview] Message-ID: <20231012042957.85ED538582BC@sourceware.org> (raw) https://gcc.gnu.org/g:ab63444d033067ee72baab1f1af16a4224eac5b2 commit ab63444d033067ee72baab1f1af16a4224eac5b2 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Oct 12 00:29:49 2023 -0400 Revert patches Diff: --- gcc/config/rs6000/rs6000.cc | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index b03913fe71b..2828f01413c 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -10370,17 +10370,6 @@ can_be_built_by_li_lis_and_rldicl (HOST_WIDE_INT c, int *shift, /* Leading zeros may be cleaned by rldicl with a mask. Change leading zeros to ones and then recheck it. */ int lz = clz_hwi (c); - - /* Different machines interpret num << shift differently if shift is at least - the number of bits in num's representation. It is explicitly undefined - behavior in the C/C++ langauges. - - In particular (-1 << 64) on an x86_64 produces -1 and (-1 << 64) on a - 64-bit PowerPC produces 0. This difference causes a cross compiler on - x86_64 to recurse until it runs out of stack. */ - if (!lz) - return false; - HOST_WIDE_INT unmask_c = c | (HOST_WIDE_INT_M1U << (HOST_BITS_PER_WIDE_INT - lz)); int n;
next reply other threads:[~2023-10-12 4:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-12 4:29 Michael Meissner [this message] 2023-10-12 21:54 Michael Meissner 2023-10-16 18:23 Michael Meissner
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=20231012042957.85ED538582BC@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).