public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98386] New: C++20 module: file exists failure and success happen alternatively for windows. Date: Sat, 19 Dec 2020 03:11:25 +0000 [thread overview] Message-ID: <bug-98386-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98386 Bug ID: 98386 Summary: C++20 module: file exists failure and success happen alternatively for windows. Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- D:\Desktop\module>g++ -c main.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native D:\Desktop\module>g++ -c hello.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native hello.cc:4:8: error: failed to write compiled module: File exists 4 | export module hello; | ^~~~~~ hello.cc:4:8: note: compiled module file is 'gcm.cache/hello.gcm' D:\Desktop\module>g++ -c hello.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native D:\Desktop\module>g++ -c hello.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native hello.cc:4:8: error: failed to write compiled module: File exists 4 | export module hello; | ^~~~~~ hello.cc:4:8: note: compiled module file is 'gcm.cache/hello.gcm' D:\Desktop\module>g++ -c hello.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native D:\Desktop\module>g++ -c hello.cc -Ofast -std=c++20 -s -flto -fmodules-ts -march=native hello.cc:4:8: error: failed to write compiled module: File exists 4 | export module hello; | ^~~~~~ hello.cc:4:8: note: compiled module file is 'gcm.cache/hello.gcm' You have a succ-error-succ-error loop. It must be something bugged here.
next reply other threads:[~2020-12-19 3:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-19 3:11 unlvsur at live dot com [this message] 2020-12-19 3:13 ` [Bug c++/98386] " unlvsur at live dot com 2020-12-19 3:18 ` unlvsur at live dot com 2020-12-21 17:06 ` nathan at gcc dot gnu.org 2020-12-21 17:11 ` nathan at gcc dot gnu.org 2020-12-21 17:12 ` unlvsur at live dot com 2020-12-21 17:14 ` nathan at gcc dot gnu.org 2020-12-21 17:35 ` unlvsur at live dot com 2020-12-21 17:43 ` nathan at gcc dot gnu.org 2020-12-21 17:45 ` unlvsur at live dot com 2020-12-21 17:46 ` unlvsur at live dot com 2020-12-21 17:51 ` nathan 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-98386-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).