public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98892] FAIL: gcc.dg/plugin/diagnostic-test-expressions-1.c Date: Thu, 03 Jun 2021 11:19:05 +0000 [thread overview] Message-ID: <bug-98892-4-6CW75FAHQY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98892-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98892 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Host|hppa-unknown-linux-gnu | Last reconfirmed| |2021-06-03 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |ebotcazou at gcc dot gnu.org Build|hppa-unknown-linux-gnu | Target|hppa-unknown-linux-gnu | --- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- I'm seeing it on x86-64/Linux as well: FAIL: gcc.dg/plugin/diagnostic-test-expressions-1.c -fplugin=./diagnostic_plugin_test_tree_expression_range.so 1 blank line(s) in output FAIL: gcc.dg/plugin/diagnostic-test-expressions-1.c -fplugin=./diagnostic_plugin_test_tree_expression_range.so expected multiline pattern lines 550-551 not found: " __builtin_types_compatible_p \\(long, int\\) \\+ f \\(i\\)\\);.*\\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\\^~~~~~~\\n" FAIL: gcc.dg/plugin/diagnostic-test-expressions-1.c -fplugin=./diagnostic_plugin_test_tree_expression_range.so (test for excess errors) but it apparently goes away and comes back.
next prev parent reply other threads:[~2021-06-03 11:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 16:44 [Bug c/98892] New: " danglin at gcc dot gnu.org 2021-06-03 11:19 ` ebotcazou at gcc dot gnu.org [this message] 2021-06-26 4:09 ` [Bug c/98892] " wilson at gcc dot gnu.org 2021-06-26 14:46 ` wilson at gcc dot gnu.org 2021-06-28 17:27 ` wilson 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-98892-4-6CW75FAHQY@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).