public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/99175] New: FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for errors, line ) Date: Fri, 19 Feb 2021 23:09:56 +0000 [thread overview] Message-ID: <bug-99175-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99175 Bug ID: 99175 Summary: FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for errors, line ) Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org Target Milestone: --- Host: hppa2.0w-hp-hpux11.11 Target: hppa2.0w-hp-hpux11.11 Build: hppa2.0w-hp-hpux11.11 spawn /test/gnu/gcc/objdir/gcc/testsuite/g++/../../xg++ -B/test/gnu/gcc/objdir/gcc/testsuite/g++/../../ /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C -fdiagnostics-plain-output -nostdinc++ -I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/include/hppa2.0w-hp-hpux11.11 -I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/include -I/test/gnu/gcc/gcc/libstdc++-v3/libsupc++ -I/test/gnu/gcc/gcc/libstdc++-v3/include/backward -I/test/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -std=c++17 -pedantic-errors -Wno-long-long -fmodules-ts -fmodule-mapper=|this-will-not-work -S -o bad-mapper-1.s cc1plus: error trying to exec 'this-will-not-work': execvp: No such file or directory /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C: error: failed mapper handshake communication error:Broken pipe /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C:2:1: error: unknown Compiled Module Interface: communication error:Broken pipe In module imported at /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C:2:1: unique1.bob: error: failed to read compiled module: Unknown CMI mapping unique1.bob: note: imports must be built before being imported unique1.bob: fatal error: returning to the gate for a mechanical issue compilation terminated. compiler exited with status 1 output is: cc1plus: error trying to exec 'this-will-not-work': execvp: No such file or directory /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C: error: failed mapper handshake communication error:Broken pipe /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C:2:1: error: unknown Compiled Module Interface: communication error:Broken pipe In module imported at /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C:2:1: unique1.bob: error: failed to read compiled module: Unknown CMI mapping unique1.bob: note: imports must be built before being imported unique1.bob: fatal error: returning to the gate for a mechanical issue compilation terminated. FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for errors, line ) FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for excess errors) Excess errors: cc1plus: error trying to exec 'this-will-not-work': execvp: No such file or directory /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C: error: failed mapper handshake communication error:Broken pipe /test/gnu/gcc/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-1.C:2:1: error: unknown Compiled Module Interface: communication error:Broken pipe
next reply other threads:[~2021-02-19 23:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-19 23:09 danglin at gcc dot gnu.org [this message] 2022-01-28 17:54 ` [Bug testsuite/99175] " danglin at gcc dot gnu.org 2022-01-28 18:10 ` [Bug c++/99175] " pinskia at gcc dot gnu.org 2022-01-28 18:14 ` [Bug testsuite/99175] " pinskia at gcc dot gnu.org 2022-01-28 21:42 ` pinskia 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-99175-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).