public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clugstj at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110368] New: Incorrect "is used uninitialized" warning message
Date: Thu, 22 Jun 2023 17:27:49 +0000 [thread overview]
Message-ID: <bug-110368-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110368
Bug ID: 110368
Summary: Incorrect "is used uninitialized" warning message
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: clugstj at gmail dot com
Target Milestone: ---
Created attachment 55384
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55384&action=edit
Code that causes warning
The attached code, when compiled with:
>gcc -O2 -Wall -Wextra -c uninit.c
results in the following error messages:
uninit.c: In function 'cksum':
uninit.c:20:13: warning: 'l' is used uninitialized [-Wuninitialized]
20 | unsigned l = len;
| ^
uninit.c:21:13: warning: 'n' is used uninitialized [-Wuninitialized]
21 | unsigned n = protocol;
| ^
next reply other threads:[~2023-06-22 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 17:27 clugstj at gmail dot com [this message]
2023-06-22 17:29 ` [Bug c/110368] " clugstj at gmail dot com
2023-06-22 17:31 ` pinskia at gcc dot gnu.org
2023-06-22 17:32 ` pinskia at gcc dot gnu.org
2023-06-22 17:35 ` pinskia at gcc dot gnu.org
2023-06-22 17:37 ` pinskia at gcc dot gnu.org
2023-10-05 16:19 ` clugstj at gmail dot com
2023-10-06 15:51 ` sjames at gcc dot gnu.org
2023-10-07 6:36 ` xry111 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-110368-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).