From: Krishna Narayanan <krishnanarayanan132002@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Extended doubt regarding the bug 93432
Date: Tue, 8 Feb 2022 22:47:55 +0530 [thread overview]
Message-ID: <CABhGnjuhTJ4M_osffb0jC807nwO7PxRjgHfgSz_ALSgYZm81TA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdSni2Dz1VXzb1cbG5ee2z3rD1Z54nWZqSN=NKz4NsDSQQ@mail.gmail.com>
Thanks for your response,Could you please clarify if this is a bug?
Regards,
Krishna Narayanan.
On Tue, Feb 8, 2022 at 10:28 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:
>
>
> On Tue, 8 Feb 2022 at 16:25, Krishna Narayanan via Gcc-help <
> gcc-help@gcc.gnu.org> wrote:
>
>> Hello,
>> As an extension to the bug 93432
>> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432), I would like to
>> add a few more points,here in the given code
>> (https://godbolt.org/z/sYjqjqh3d) there is a warning averted but there
>> is no warning shown for this code
>> (https://gcc.godbolt.org/z/oo5sf4oec) .
>> I tried it with "-fno-strict-aliasing -fwrapv
>> -fno-aggressive-loop-optimizations" and "fsanitize=undefined".There
>> are no errors for gcc but clang has runtime errors,the error for
>> clang: https://gcc.godbolt.org/z/1hq8x1o8E .
>>
>> Can we have a warning in the second case as well? It will be much more
>> convenient as there is a lapse of initialization.
>>
>
> Yes, ideally it would warn.
>
>
>
next prev parent reply other threads:[~2022-02-08 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:24 Krishna Narayanan
2022-02-08 16:58 ` Jonathan Wakely
2022-02-08 17:17 ` Krishna Narayanan [this message]
2022-02-08 17:37 ` Jonathan Wakely
2022-02-08 17:47 ` Krishna Narayanan
2022-02-08 21:50 ` Martin Sebor
2022-02-09 5:06 ` Krishna Narayanan
2022-02-11 18:10 ` Krishna Narayanan
2022-02-14 15:24 ` Martin Sebor
[not found] ` <CABhGnjvSO8svWrBNiO3aKJDjZ5mx2pE-kKgH-0pmyBYjLTwBRw@mail.gmail.com>
2022-02-14 20:22 ` Martin Sebor
2022-02-15 12:10 ` Krishna Narayanan
2022-02-16 21:27 ` Martin Sebor
2022-02-19 13:38 ` Krishna Narayanan
2022-02-09 16:59 ` Segher Boessenkool
2022-02-09 18:43 ` Krishna Narayanan
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=CABhGnjuhTJ4M_osffb0jC807nwO7PxRjgHfgSz_ALSgYZm81TA@mail.gmail.com \
--to=krishnanarayanan132002@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).