public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/104150] New: New test case gcc.dg/analyzer/pr104089.c fails after its introduction in r12-6700 Date: Thu, 20 Jan 2022 23:23:34 +0000 [thread overview] Message-ID: <bug-104150-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104150 Bug ID: 104150 Summary: New test case gcc.dg/analyzer/pr104089.c fails after its introduction in r12-6700 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:2aefe248aa4160205c44808166393a42031d2dea, r12-6700 make -k check-gcc RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/pr104089.c" FAIL: gcc.dg/analyzer/pr104089.c (test for excess errors) # of unexpected failures 1 This new test does stuff not supported everywhere. Excess errors: /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr104089.c:3:10: error: '_Float16' is not supported on this target /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr104089.c:3:1: error: unsupported non-standard suffix on floating constant /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr104089.c:8:47: error: non-floating-point argument in call to function '__builtin_fpclassify' commit 2aefe248aa4160205c44808166393a42031d2dea (HEAD, refs/bisect/bad) Author: David Malcolm <dmalcolm@redhat.com> Date: Tue Jan 18 11:41:19 2022 -0500 analyzer: fix ICE on unary ops folding to casts of constants [PR104089] gcc/testsuite/ChangeLog: * gcc.dg/analyzer/pr104089.c: New test. PR analyzer/104089
next reply other threads:[~2022-01-20 23:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 23:23 seurer at gcc dot gnu.org [this message] 2022-01-22 15:27 ` [Bug analyzer/104150] " cvs-commit at gcc dot gnu.org 2022-01-22 15:44 ` dmalcolm 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-104150-4@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).