public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at kam dot mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103230] ipa-modref-tree.h:550:33: runtime error: load of value 255, which is not a valid value for type 'bool'
Date: Sun, 14 Nov 2021 09:21:36 +0000 [thread overview]
Message-ID: <bug-103230-4-NI8pGsu7Kx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103230-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103230
--- Comment #1 from hubicka at kam dot mff.cuni.cz ---
> Happens with UBSAN compiler for:
>
> $ gcc gcc/testsuite/gcc.c-torture/execute/pr71494.c -O1 -flto
> ...
> /home/marxin/Programming/gcc/gcc/ipa-modref-tree.h:550:33: runtime error: load
> of value 255, which is not a valid value for type 'bool'
> #0 0x18acc38 in modref_tree<tree_node*>::merge(modref_tree<tree_node*>*,
> vec<modref_parm_map, va_heap, vl_ptr>*, modref_parm_map*, bool)
> /home/marxin/Programming/gcc/gcc/ipa-modref-tree.h:550
> #1 0x188452c in modref_propagate_in_scc
At 4385 I have:
changed |= cur_summary_lto->stores->merge
(callee_summary_lto->stores, &parm_map, &chain_map, !first);
parm-map is the vector, however there is no read of it.
There is bool which is relevant only when parm_index is not unknown, so
I suspect it may a full copy with uninitialized bool which would be
harmless. We had similar issues with asan before.
How do you build ubsan compiler?
Honza
next prev parent reply other threads:[~2021-11-14 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 8:55 [Bug ipa/103230] New: " marxin at gcc dot gnu.org
2021-11-14 8:56 ` [Bug ipa/103230] " marxin at gcc dot gnu.org
2021-11-14 9:21 ` [Bug ipa/103230] New: " Jan Hubicka
2021-11-14 9:21 ` hubicka at kam dot mff.cuni.cz [this message]
2021-11-14 9:26 ` [Bug ipa/103230] " marxin at gcc dot gnu.org
2021-11-14 9:47 ` Jan Hubicka
2021-11-14 9:47 ` hubicka at kam dot mff.cuni.cz
2021-11-14 10:01 ` marxin at gcc dot gnu.org
2021-11-14 10:04 ` marxin at gcc dot gnu.org
2021-11-16 8:46 ` marxin at gcc dot gnu.org
2021-11-18 9:30 ` pinskia at gcc dot gnu.org
2021-11-18 12:12 ` marxin at gcc dot gnu.org
2021-11-19 11:33 ` cvs-commit at gcc dot gnu.org
2021-11-19 11:34 ` marxin 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-103230-4-NI8pGsu7Kx@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).