public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115026] msp430-elf fails gcc.dg/pr66444.c with prange enabled
Date: Fri, 10 May 2024 10:36:41 +0000	[thread overview]
Message-ID: <bug-115026-4-GIB58mEf9h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115026-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
OK, this is embarrassing.

We are incorrectly folding a POINTER_PLUS_EXPR range operation:

 Folding statement: x_7 = 2048B + _2;
-Queued stmt for removal.  Folds to: 2062B
+Queued stmt for removal.  Folds to: 0B

The reason is that the prange::update_bitmask() code is ignoring its operand
and using the current bitmask.

I have no idea how this bootstrapped *any* architecture.  I suppose it needs a
value/mask pair (0xe / 0x0) for the second operand that actually indicates a
singleton.  *shrug*

Thanks for reporting this.

  parent reply	other threads:[~2024-05-10 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  9:42 [Bug tree-optimization/115026] New: " aldyh at gcc dot gnu.org
2024-05-10  9:43 ` [Bug tree-optimization/115026] " aldyh at gcc dot gnu.org
2024-05-10 10:36 ` aldyh at gcc dot gnu.org [this message]
2024-05-10 10:37 ` aldyh at gcc dot gnu.org
2024-05-10 10:38 ` aldyh at gcc dot gnu.org
2024-05-10 12:41 ` [Bug tree-optimization/115026] [15 Regression] " rguenth at gcc dot gnu.org
2024-05-10 14:57 ` cvs-commit at gcc dot gnu.org
2024-05-10 15:09 ` aldyh at gcc dot gnu.org
2024-05-10 18:01 ` law at gcc dot gnu.org
2024-05-10 20:57 ` aldyh 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-115026-4-GIB58mEf9h@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).