public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98529] New: g++.dg/modules/stdio-1_a.H FAILs Date: Tue, 05 Jan 2021 12:42:27 +0000 [thread overview] Message-ID: <bug-98529-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98529 Bug ID: 98529 Summary: g++.dg/modules/stdio-1_a.H FAILs Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: nathan at gcc dot gnu.org Target Milestone: --- Target: i386-pc-solaris2.11 Created attachment 49885 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49885&action=edit i386-pc-solaris2.11 32-bit stdio-1_a.H.002l.module The new g++.dg/modules/stdio-1_a.H test FAILs on Solaris/x86 (only): +FAIL: g++.dg/modules/stdio-1_a.H -std=c++17 scan-lang-dump module "Depset:0 decl entity:[0-9]* function_decl:'::printf'" +FAIL: g++.dg/modules/stdio-1_a.H -std=c++2a scan-lang-dump module "Depset:0 decl entity:[0-9]* function_decl:'::printf'" I'm attaching the .module file.
next reply other threads:[~2021-01-05 12:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-05 12:42 ro at gcc dot gnu.org [this message] 2021-01-05 12:42 ` [Bug c++/98529] " ro at gcc dot gnu.org 2021-01-05 13:46 ` nathan at gcc dot gnu.org 2021-01-05 13:49 ` ro at gcc dot gnu.org 2021-04-09 8:03 ` [Bug c++/98529] [11 Regression] " rguenth at gcc dot gnu.org 2021-04-14 12:12 ` ro at gcc dot gnu.org 2021-04-27 11:40 ` [Bug c++/98529] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-03-23 8:33 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` [Bug c++/98529] [11/12/13/14 " jakub at gcc dot gnu.org 2024-05-10 12:39 ` [Bug c++/98529] [11/12/13/14/15 " ro at gcc dot gnu.org 2024-05-13 8:43 ` ro at gcc dot gnu.org 2024-05-13 12:03 ` cvs-commit at gcc dot gnu.org 2024-05-13 12:04 ` ro 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-98529-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).