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 tree-optimization/107286] gcc/value-range.cc:4027: range_tests_floats: FAIL: ASSERT_TRUE ((real_isinf (&r0.lower_bound (), true))) Date: Mon, 17 Oct 2022 08:00:47 +0000 [thread overview] Message-ID: <bug-107286-4-eB4US0Q9uD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107286-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107286 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|--- |13.0 Host| |x86_64-linux-gnu Status|UNCONFIRMED |NEW Last reconfirmed| |2022-10-17 --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Note the test was added in r13-3305-g3dfeda095bd43c.
next prev parent reply other threads:[~2022-10-17 8:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-17 8:00 [Bug tree-optimization/107286] New: " marxin at gcc dot gnu.org 2022-10-17 8:00 ` marxin at gcc dot gnu.org [this message] 2022-10-17 13:29 ` [Bug tree-optimization/107286] " cvs-commit at gcc dot gnu.org 2022-10-17 13:29 ` aldyh 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-107286-4-eB4US0Q9uD@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: linkBe 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).