public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98362] bad file data on Windows for C++ 20 module Date: Fri, 18 Dec 2020 12:48:27 +0000 [thread overview] Message-ID: <bug-98362-4-b0kYu2iZIK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98362-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98362 Nathan Sidwell <nathan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2020-12-18 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot gnu.org --- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> --- ah, I didn't know the binary/text distinction descended below the FILE level on windows
next prev parent reply other threads:[~2020-12-18 12:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 22:57 [Bug c++/98362] New: " unlvsur at live dot com 2020-12-18 12:48 ` nathan at gcc dot gnu.org [this message] 2020-12-18 13:38 ` [Bug c++/98362] " nathan at gcc dot gnu.org 2020-12-18 13:44 ` unlvsur at live dot com 2020-12-18 13:48 ` unlvsur at live dot com 2020-12-18 14:56 ` unlvsur at live dot com 2020-12-18 15:39 ` nathan at gcc dot gnu.org 2020-12-19 2:00 ` unlvsur at live dot com
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-98362-4-b0kYu2iZIK@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).