public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106008] [11/12 Regression] warning: ‘(((char *)loadcmds.113_68 + _933 + 16))[329406144173384849].mapend’ may be used uninitialized [-Wmaybe-uninitialized]
Date: Fri, 17 Jun 2022 02:55:20 +0000 [thread overview]
Message-ID: <bug-106008-4-tqMh4NN3dc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106008-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106008
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|12.0 |11.2.1
Summary|[12 Regression] warning: |[11/12 Regression] warning:
|‘(((char *)loadcmds.113_68 |‘(((char *)loadcmds.113_68
|+ _933 + |+ _933 +
|16))[329406144173384849].ma |16))[329406144173384849].ma
|pend’ may be used |pend’ may be used
|uninitialized |uninitialized
|[-Wmaybe-uninitialized] |[-Wmaybe-uninitialized]
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
GCC 11 has the same issue.
next prev parent reply other threads:[~2022-06-17 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 19:16 [Bug middle-end/106008] New: [12 " hjl.tools at gmail dot com
2022-06-16 22:27 ` [Bug middle-end/106008] " hjl.tools at gmail dot com
2022-06-17 2:55 ` hjl.tools at gmail dot com [this message]
2022-06-20 10:01 ` [Bug middle-end/106008] [11/12/13 " rguenth at gcc dot gnu.org
2022-06-20 10:01 ` rguenth at gcc dot gnu.org
2023-03-29 13:35 ` rguenth at gcc dot gnu.org
2023-05-29 10:07 ` [Bug middle-end/106008] [11/12/13/14 " jakub 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-106008-4-tqMh4NN3dc@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).