public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106186] New: [13 regression] Recent change causing target regressions for uninitialized objects
Date: Mon, 04 Jul 2022 15:54:03 +0000 [thread overview]
Message-ID: <bug-106186-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106186
Bug ID: 106186
Summary: [13 regression] Recent change causing target
regressions for uninitialized objects
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
This change:
commit 4e82205b68024f5c1a9006fe2b62e1a0fa7f1245
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Fri Jul 1 13:20:42 2022 +0200
Integrate nonzero bits with irange.
The nonzero bits and integer ranges compliment each other quite well,
and it only makes sense to make the mask a first class citizen in the
irange. We do a half assed job of keeping ranges and nonzero bits
somewhat in sync in SSA_NAME_RANGE_INFO, and the goal has always
been to integrate them properly. This patch does that, in preparation
for streaming out full-resolution iranges between passes (think
SSA_NAME_RANGE_INFO).
[ ... ]
Has caused several targets to start failing this test:
Tests that now fail, but worked before (1 tests):
cris-sim: gcc.dg/auto-init-uninit-4.c (test for excess errors)
>From the gcc.log file:
Excess errors:
/home/jlaw/test/gcc/gcc/testsuite/gcc.dg/uninit-4.c:49:10: warning: 'rprio' may
be used uninitialized [-Wmaybe-uninitialized]
This should be visible with just a cross compiler.
Testcase not explicitly included as it's obvious this is gcc.dg/uninit-4.c in
the testsuite.
next reply other threads:[~2022-07-04 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 15:54 law at gcc dot gnu.org [this message]
2022-07-04 18:56 ` [Bug tree-optimization/106186] " aldyh at gcc dot gnu.org
2022-07-05 7:49 ` rguenth at gcc dot gnu.org
2022-07-05 9:22 ` rguenth at gcc dot gnu.org
2022-07-05 9:22 ` rguenth at gcc dot gnu.org
2022-07-05 9:38 ` rguenth at gcc dot gnu.org
2022-07-05 12:12 ` cvs-commit at gcc dot gnu.org
2022-07-05 12:12 ` rguenth at gcc dot gnu.org
2022-07-05 15:37 ` law at gcc dot gnu.org
2022-07-05 15:51 ` 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-106186-4@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).