public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112909] New: [14 Regression] glibc -Wuninitialized build failure for i686-gnu
Date: Thu, 07 Dec 2023 22:10:38 +0000 [thread overview]
Message-ID: <bug-112909-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112909
Bug ID: 112909
Summary: [14 Regression] glibc -Wuninitialized build failure
for i686-gnu
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: aldyh at gcc dot gnu.org
Target Milestone: ---
Target: i?86-*-*
Created attachment 56829
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56829&action=edit
preprocessed source
What look like spurious -Wuninitialized errors were introduced building glibc
for i686-gnu (Hurd) by:
commit 602e824eec30a7c6792b8b27d61c40f1c1a2714c
Author: Aldy Hernandez <aldyh@redhat.com>
AuthorDate: Thu Jun 29 11:27:49 2023 +0200
Commit: Aldy Hernandez <aldyh@redhat.com>
CommitDate: Wed Jul 12 18:21:29 2023 +0200
[range-op] Enable value/mask propagation in range-op.
Compile the attached test for i686-gnu with -O2 -Wall -Werror (likely the issue
appears also as a regression for other targets, the source file in glibc that
this came from is Hurd-specific so it wouldn't have broken the glibc build for
other targets).
../sysdeps/mach/hurd/x86/trampoline.c: In function '_hurd_setup_sighandler':
../sysdeps/mach/hurd/x86/trampoline.c:108:22: error: 'scp' may be used
uninitialized [-Werror=maybe-uninitialized]
108 | struct sigcontext *scp;
| ^~~
../sysdeps/mach/hurd/x86/trampoline.c:353:34: error: 'args' may be used
uninitialized [-Werror=maybe-uninitialized]
353 | struct mach_msg_trap_args *args = (void *) state->basic.esp;
| ^~~~
cc1: all warnings being treated as errors
I don't see any way these variables can be used uninitialized, even taking into
account the use of setjmp in this function which could well be confusing
things.
next reply other threads:[~2023-12-07 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 22:10 jsm28 at gcc dot gnu.org [this message]
2023-12-08 6:57 ` [Bug middle-end/112909] " rguenth at gcc dot gnu.org
2023-12-08 7:56 ` rguenth at gcc dot gnu.org
2023-12-08 8:14 ` rguenth at gcc dot gnu.org
2023-12-08 10:32 ` cvs-commit at gcc dot gnu.org
2023-12-08 10:33 ` rguenth 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-112909-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).