From: Alejandro Colomar <alx.manpages@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc@gcc.gnu.org, Martin Uecker <uecker@tugraz.at>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [BUG] -Wuninitialized: initialize variable with itself
Date: Sun, 13 Nov 2022 19:43:51 +0100 [thread overview]
Message-ID: <4e8d0be6-37f0-2478-a46a-730745313b70@gmail.com> (raw)
In-Reply-To: <CA+=Sn1==xkbSzE+Gb_P6T8yQVhiOHSPXx_sze8Xp-o7+gNVj4Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]
Hi Andrew!
On 11/13/22 19:41, Andrew Pinski wrote:
> On Sun, Nov 13, 2022 at 10:40 AM Andrew Pinski <pinskia@gmail.com> wrote:
>>
>> On Sun, Nov 13, 2022 at 10:36 AM Alejandro Colomar via Gcc
>> <gcc@gcc.gnu.org> wrote:
>>>
>>> Hi,
>>>
>>> While discussing some idea for a new feature, I tested the following example
>>> program:
>>>
>>>
>>> int main(void)
>>> {
>>> int i = i;
>>> return i;
>>> }
>>
>> This is NOT a bug but a documented way of having the warning not being there.
>> See https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Warning-Options.html#index-Winit-self
>> https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Warning-Options.html#index-Wuninitialized
>> "If you want to warn about code that uses the uninitialized value of
>> the variable in its own initializer, use the -Winit-self option."
>
> I should note the main reason why I Know about this is because I fixed
> this feature years ago (at least for C front-end)
> and added the option to disable the feature.
I'm curious: what are the reasons why one would want to disable such a warning?
Why is it not in -Wall or -Wextra?
Thanks,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-13 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 18:34 Alejandro Colomar
2022-11-13 18:40 ` Andrew Pinski
2022-11-13 18:41 ` Andrew Pinski
2022-11-13 18:43 ` Alejandro Colomar [this message]
2022-11-14 9:41 ` David Brown
2022-11-14 11:30 ` Alejandro Colomar
2022-11-14 15:10 ` NightStrike
2022-11-14 15:49 ` David Brown
2022-11-14 17:43 ` NightStrike
2022-11-13 18:45 ` Andrew Pinski
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=4e8d0be6-37f0-2478-a46a-730745313b70@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=pinskia@gmail.com \
--cc=uecker@tugraz.at \
/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).