public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "deco33000 at yandex dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101780] Missing initializers whereas structure has default initializers Date: Thu, 05 Aug 2021 14:17:49 +0000 [thread overview] Message-ID: <bug-101780-4-uVTnXnHpRu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101780-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101780 --- Comment #2 from KL <deco33000 at yandex dot com> --- (In reply to Jonathan Wakely from comment #1) Thanks, I thought that this warning is fine if it helps to assure the developer that everything is still under control: that if the analyzer sees that a field is left uninitialized (with no default value), it should tell it in this warning. > How would P,Q,R be left uninitialized? Only if the analyzer has the info that, at this stage, there no default value for the field. It could be interesting in the context of a partially initialized struct (by mistake, intended by the developer?)? It help with quality of code. > It doesn't say anything about undefined behaviour. In case the developer forgot to properly initialize a member, it *can* lead to undefined behavior. So, it is good from the compiler to warn about it as well.
next prev parent reply other threads:[~2021-08-05 14:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 19:53 [Bug c++/101780] New: " deco33000 at yandex dot com 2021-08-05 11:39 ` [Bug c++/101780] " redi at gcc dot gnu.org 2021-08-05 14:17 ` deco33000 at yandex dot com [this message] 2021-08-05 16:00 ` redi at gcc dot gnu.org 2021-08-06 5:01 ` deco33000 at yandex dot com 2023-05-04 16:11 ` pinskia 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-101780-4-uVTnXnHpRu@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: linkBe 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).