public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c
Date: Thu, 17 Nov 2022 12:01:28 +0000	[thread overview]
Message-ID: <bug-107734-4-Ehreix6ttY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107734-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734

--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---

Another test case:

./gcc.target/i386/pr53366-2.c
==666641== Conditional jump or move depends on uninitialised value(s)
==666641==    at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137)
==666641==    by 0x11DFAE7: gimple_simplify_122(gimple_match_op*, gimple**,
tree_node* (*)(tree_node*), tree_node*, tree_node**, tree_code)
(gimple-match.cc:48933)

  parent reply	other threads:[~2022-11-17 12:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 11:45 [Bug c/107734] New: " dcb314 at hotmail dot com
2022-11-17 11:47 ` [Bug c/107734] " dcb314 at hotmail dot com
2022-11-17 11:59 ` dcb314 at hotmail dot com
2022-11-17 12:01 ` dcb314 at hotmail dot com [this message]
2022-11-17 13:38 ` dcb314 at hotmail dot com
2022-11-17 17:01 ` dcb314 at hotmail dot com
2022-11-17 17:06 ` dcb314 at hotmail dot com
2022-11-17 17:38 ` [Bug middle-end/107734] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-17 17:59 ` cvs-commit at gcc dot gnu.org
2022-11-17 18:00 ` pinskia at gcc dot gnu.org
2022-11-17 19:43 ` dcb314 at hotmail dot com
2022-11-17 20:01 ` pinskia at gcc dot gnu.org
2022-11-18  8:12 ` wwwhhhyyy333 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-107734-4-Ehreix6ttY@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).