public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104738] gdc.test/runnable_cxx/stdint.d FAILs on Solaris
Date: Wed, 02 Mar 2022 09:58:27 +0000 [thread overview]
Message-ID: <bug-104738-4-kNMGKRDMZE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104738
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
> In upstream druntime, stdint aliases were refactored to commonize so-called
> "platform-independent" typedefs.
>
> As you've pointed out, none of the stdint types are platform independent at
> all. i.e: Compare any `<target>-stdint.h' header.
Right, and those differences usually are usually dictated by the various
psABIs and cannot be changed. Quirks like char being signed on Solaris
may be uncommon, but well within the standard's requirements. I had a
couple of related issues in LLVM e.g.
next prev parent reply other threads:[~2022-03-02 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:20 [Bug d/104738] New: " ro at gcc dot gnu.org
2022-03-01 12:21 ` [Bug d/104738] " ro at gcc dot gnu.org
2022-03-01 21:13 ` ibuclaw at gdcproject dot org
2022-03-02 9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-03-02 22:20 ` joseph at codesourcery dot com
2022-03-13 13:18 ` 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-104738-4-kNMGKRDMZE@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).