public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102030] Optimization turns null ptr true
Date: Tue, 24 Aug 2021 01:45:59 +0000 [thread overview]
Message-ID: <bug-102030-4-OUP8sCDQXr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102030-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102030
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
BM_mesh_bm_from_me has the nonnull attribute on it for ob saying if ob is a
null argument passed to it undefined behavior will happen. So obviously it
will remove the comparisons.
These warnings here:
/home/joeedh/blender/blender/build/bmesh_mesh_convert_bugreport.c: In function
'BM_mesh_bm_from_me':
/home/joeedh/blender/blender/build/bmesh_mesh_convert_bugreport.c:357:6:
warning: 'nonnull' argument 'ob' compared to NULL [-Wnonnull-compare]
/home/joeedh/blender/blender/build/bmesh_mesh_convert_bugreport.c:335:6:
warning: 'nonnull' argument 'ob' compared to NULL [-Wnonnull-compare]
/home/joeedh/blender/blender/build/bmesh_mesh_convert_bugreport.c:320:3:
warning: 'nonnull' argument 'ob' compared to NULL [-Wnonnull-compare]
Are the important ones to pay attention to.
next prev parent reply other threads:[~2021-08-24 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 23:34 [Bug c/102030] New: " joeedh at gmail dot com
2021-08-23 23:38 ` [Bug c/102030] " joeedh at gmail dot com
2021-08-24 1:41 ` pinskia at gcc dot gnu.org
2021-08-24 1:45 ` pinskia at gcc dot gnu.org [this message]
2021-08-27 3:21 ` joeedh at gmail dot com
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-102030-4-OUP8sCDQXr@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).