public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/91595] Version (Windows) is not defined in GCC D Compiler
Date: Sun, 21 Mar 2021 14:18:44 +0000 [thread overview]
Message-ID: <bug-91595-4-I4x7r4xrCC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91595-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91595
--- Comment #11 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Brecht Sanders from comment #10)
> I thought MinGW-w64 is it's own C library.
> It is found by GCC build process because the folder mingw exists in the
> location specified with --with-build-sysroot
>
Right, so there will need to be some porting done to add `version (MinGW)`
blocks to druntime in order to define all bindings that are tied to a specific
C library - such as core/stdc/stdio.d.
> CppRuntime_Gcc is mentioned in the predefs, why would CRuntime_Gcc not be
> defined then?
CppRuntime_Gcc is for libstdc++, the other C++ runtime library is MSVC++, which
GCC is not compatible with. There is no C runtime library included with GCC.
next prev parent reply other threads:[~2021-03-21 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91595-4@http.gcc.gnu.org/bugzilla/>
2020-03-22 0:08 ` ibuclaw at gdcproject dot org
2020-03-22 0:09 ` ibuclaw at gdcproject dot org
2020-03-22 0:16 ` ibuclaw at gdcproject dot org
2021-03-21 9:56 ` brechtsanders at users dot sourceforge.net
2021-03-21 10:30 ` ibuclaw at gdcproject dot org
2021-03-21 13:11 ` brechtsanders at users dot sourceforge.net
2021-03-21 13:20 ` ibuclaw at gdcproject dot org
2021-03-21 13:27 ` brechtsanders at users dot sourceforge.net
2021-03-21 13:44 ` ibuclaw at gdcproject dot org
2021-03-21 13:51 ` brechtsanders at users dot sourceforge.net
2021-03-21 14:18 ` ibuclaw at gdcproject dot org [this message]
2021-03-26 15:15 ` cvs-commit at gcc dot gnu.org
2021-03-26 15:50 ` ibuclaw at gdcproject dot 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-91595-4-I4x7r4xrCC@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: link
Be 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).