public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/96482] [10/11 Regression] Combination of -finline-small-functions and ipa-cp optimisations causes incorrect values being passed to a function since r279523
Date: Tue, 11 Aug 2020 15:12:52 +0000 [thread overview]
Message-ID: <bug-96482-4-4CtwPwtV70@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96482-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96482
--- Comment #13 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #11)
> But streamed IPA CP info tells that:
>
> Node: addr_to_offset/632014:
> param [0]: VARIABLE
> ctxs: VARIABLE
> Bits: value = 0x0, mask = 0xfffffffffffffff8
> int VARYING
> AGGS VARIABLE
> param [1]: VARIABLE
> ctxs: VARIABLE
> Bits unusable (BOTTOM)
> int VARYING
> AGGS VARIABLE
> param [2]: 5 [loc_time: 4, loc_size: 2, prop_time: 0, prop_size: 0]
> 3 [loc_time: 3, loc_size: 10, prop_time: 0, prop_size: 0]
> ctxs: VARIABLE
> Bits: value = 0x5, mask = 0x6
> int VARYING
> AGGS VARIABLE
>
> So param[2] is either 5 or 3. Interesting..
That's correct as there's really one call chain that eventually calls
addr_to_offset with value equal to 5. That's UBSAN and this does not happen
during run-time. I'm debugging deeper..
next prev parent reply other threads:[~2020-08-11 15:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 11:24 [Bug c/96482] New: Combination of -finline-small-functions and ipa-cp optimisations causes incorrect values being passed to a function yevh.kolesnikov at gmail dot com
2020-08-05 11:27 ` [Bug c/96482] " yevh.kolesnikov at gmail dot com
2020-08-05 11:37 ` [Bug ipa/96482] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-08-10 7:29 ` [Bug ipa/96482] [10/11 Regression] Combination of -finline-small-functions and ipa-cp optimisations causes incorrect values being passed to a function since r279523 marxin at gcc dot gnu.org
2020-08-10 7:41 ` hubicka at gcc dot gnu.org
2020-08-10 14:24 ` yevh.kolesnikov at gmail dot com
2020-08-10 16:58 ` yevh.kolesnikov at gmail dot com
2020-08-10 20:00 ` marxin at gcc dot gnu.org
2020-08-11 7:08 ` marxin at gcc dot gnu.org
2020-08-11 7:59 ` marxin at gcc dot gnu.org
2020-08-11 7:59 ` marxin at gcc dot gnu.org
2020-08-11 8:02 ` marxin at gcc dot gnu.org
2020-08-11 9:39 ` marxin at gcc dot gnu.org
2020-08-11 15:12 ` marxin at gcc dot gnu.org [this message]
2020-08-11 15:33 ` marxin at gcc dot gnu.org
2020-08-11 15:51 ` marxin at gcc dot gnu.org
2020-08-11 16:09 ` marxin at gcc dot gnu.org
2020-08-12 7:38 ` marxin at gcc dot gnu.org
2020-08-12 17:06 ` cvs-commit at gcc dot gnu.org
2020-08-12 17:07 ` [Bug ipa/96482] [10 " marxin at gcc dot gnu.org
2020-08-12 17:40 ` cvs-commit at gcc dot gnu.org
2020-08-12 17:41 ` marxin at gcc dot gnu.org
2020-08-13 8:27 ` cvs-commit at gcc dot gnu.org
2020-08-13 14:12 ` cvs-commit 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-96482-4-4CtwPwtV70@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).