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 07:08:42 +0000	[thread overview]
Message-ID: <bug-96482-4-x6xfjjAl5J@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 #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Using the current master, -fdbg-cnt=ipa_cp_bits:10461 is first bad debug
counter value where (for
./src/gallium/targets/dri/libgallium_dri.so.wpa.076i.cp):

diff -u /tmp/good.txt /tmp/bad.txt
--- /tmp/good.txt       2020-08-10 23:29:57.234088465 +0200
+++ /tmp/bad.txt        2020-08-10 23:29:08.770350453 +0200
@@ -1414132,9 +1414132,10 @@
  param 2: value = 0x0, mask = 0xffffffff
 Propagated bits info for function nir_build_alu/631438:
  param 1: value = 0x110, mask = 0x1ff
-***dbgcnt: upper limit 10460 reached for ipa_cp_bits.***
 Propagated bits info for function addr_to_offset/632014:
  param 0: value = 0x0, mask = 0xfffffffffffffff8
+***dbgcnt: upper limit 10461 reached for ipa_cp_bits.***
+ param 2: value = 0x5, mask = 0x6
 Not considering _mesa_create_marshal_table/305172 for ipa bitwise propagation
; -fipa-bit-cp: disabled.
 Not considering pipe_reference_described.constprop/1065632 for VR discovery
and propagate; -fipa-ipa-vrp: disabled.
 Not considering pipe_resource_reference.constprop/1065631 for VR discovery and
propagate; -fipa-ipa-vrp: disabled.

  parent reply	other threads:[~2020-08-11  7:08 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 [this message]
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
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-x6xfjjAl5J@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).