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/104694] New: New test case g++.dg/pr104540.C has excess errors Date: Fri, 25 Feb 2022 18:33:02 +0000 [thread overview] Message-ID: <bug-104694-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104694 Bug ID: 104694 Summary: New test case g++.dg/pr104540.C has excess errors 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:a026b67f8f70d6cf35daf42a4b0909f78c9d7f40, r12-7382-ga026b67f8f70d6 make -k check-gcc RUNTESTFLAGS="dg.exp=g++.dg/pr104540.C" FAIL: g++.dg/pr104540.C -std=gnu++98 (test for excess errors) FAIL: g++.dg/pr104540.C -std=gnu++14 (test for excess errors) FAIL: g++.dg/pr104540.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/pr104540.C -std=gnu++20 (test for excess errors) # of unexpected failures 4 Excess errors: xg++: error: unrecognized command-line option '-mforce-drap' xg++: error: unrecognized command-line option '-mstackrealign' Are those some sort of target specific options perhaps? commit a026b67f8f70d6cf35daf42a4b0909f78c9d7f40 (HEAD, refs/bisect/bad) Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Feb 24 22:03:34 2022 -0300 Cope with NULL dw_cfi_cfa_loc
next reply other threads:[~2022-02-25 18:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-25 18:33 seurer at gcc dot gnu.org [this message] 2022-02-25 18:34 ` [Bug testsuite/104694] " mpolacek 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-104694-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).