public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67433] ?: expression returns unexpected value when condition is a bool variable which memory is not true/false
Date: Wed, 02 Sep 2015 09:17:00 -0000 [thread overview]
Message-ID: <bug-67433-4-276TdeRnqR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67433-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67433
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trippels at gcc dot gnu.org
--- Comment #9 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to xuejuncao from comment #8)
> thanks, i get the below result with -fsanitize=undefined
>
> boolmagic.c:12:16: runtime error: load of value 255, which is not a valid
> value for type '_Bool'
> boolmagic.c:13:15: runtime error: load of value 255, which is not a valid
> value for type '_Bool'
> boolmagic.c:14:15: runtime error: load of value 255, which is not a valid
> value for type '_Bool'
> b = 1, i = 1, j = 1
>
> but, can i say the "-fsanitize=undefined" will _corrects_ the undefined
> behaviour?
>
> or replace the code by if/else, which works fine (lucky?)
>
> int i; // = (u.b ? 1 : 0);
> if (u.b) i = 1; else i = 0;
No, you're still invoking undefined behavior. -fsanitize=undefined will not
fix this at all; it just points out the issues.
You need to get rid of the underlying problem, but this is not the place
to discuss this further.
next prev parent reply other threads:[~2015-09-02 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-67433-4@http.gcc.gnu.org/bugzilla/>
2015-09-02 7:53 ` xuejuncao at gmail dot com
2015-09-02 7:58 ` pinskia at gcc dot gnu.org
2015-09-02 8:11 ` xuejuncao at gmail dot com
2015-09-02 8:20 ` xuejuncao at gmail dot com
2015-09-02 8:21 ` pinskia at gcc dot gnu.org
2015-09-02 8:22 ` pinskia at gcc dot gnu.org
2015-09-02 8:33 ` pinskia at gcc dot gnu.org
2015-09-02 9:17 ` trippels at gcc dot gnu.org [this message]
2015-09-02 10:15 ` xuejuncao at gmail dot com
2015-09-02 10:20 ` rguenth at gcc dot gnu.org
2015-09-02 10:59 ` xuejuncao 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-67433-4-276TdeRnqR@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).