public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "syq at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103604] [12 Regression] trunk 20210506 fails to build in libphobos on mips64el-linux-gnu
Date: Tue, 14 Dec 2021 15:28:02 +0000 [thread overview]
Message-ID: <bug-103604-4-9tDciITYvC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103604-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103604
--- Comment #17 from YunQiang Su <syq at debian dot org> ---
(In reply to Iain Buclaw from comment #16)
> (In reply to Iain Buclaw from comment #15)
> > Don't think it would fail now the statically allocated size is *at least*
> > same as C. But some alias is still not matching up.
> core.sys.posix.sys.types is implicitly assuming X86 sizes.
(In reply to YunQiang Su from comment #13)
> And please have a wait, I need to make sure that this patch can work with
> N32.
Finally, with help of gdb, This patch can work with both N64 and N32.
--- /usr/lib/gcc/mips64el-linux-gnuabi64/11/include/d/core/sys/posix/sys/stat.d
2021-11-18 20:24:46.000000000 +0000
+++ stat.d 2021-12-14 15:22:21.929556158 +0000
@@ -345,7 +345,7 @@
{
struct stat_t
{
- c_ulong st_dev;
+ ulong st_dev;
int[3] st_pad1;
static if (!__USE_FILE_OFFSET64)
{
@@ -353,13 +353,13 @@
}
else
{
- c_ulong st_ino;
+ ulong st_ino;
}
mode_t st_mode;
nlink_t st_nlink;
uid_t st_uid;
gid_t st_gid;
- c_ulong st_rdev;
+ ulong st_rdev;
static if (!__USE_FILE_OFFSET64)
{
uint[2] st_pad2;
@@ -368,8 +368,8 @@
}
else
{
- c_long[3] st_pad2;
- c_long st_size;
+ uint[3] st_pad2;
+ long st_size;
}
static if (__USE_MISC || __USE_XOPEN2K8)
{
@@ -400,9 +400,9 @@
}
else
{
- c_long st_blocks;
+ long st_blocks;
}
- c_long[14] st_pad5;
+ uint[14] st_pad5;
}
}
else version (PPC)
next prev parent reply other threads:[~2021-12-14 15:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 13:23 [Bug d/103604] New: " doko at debian dot org
2021-12-07 13:31 ` [Bug d/103604] " rguenth at gcc dot gnu.org
2021-12-07 13:41 ` marxin at gcc dot gnu.org
2021-12-13 1:56 ` syq at debian dot org
2021-12-13 7:56 ` syq at debian dot org
2021-12-13 8:02 ` syq at debian dot org
2021-12-13 8:16 ` ibuclaw at gcc dot gnu.org
2021-12-13 10:40 ` syq at debian dot org
2021-12-13 10:42 ` syq at debian dot org
2021-12-13 10:44 ` ibuclaw at gcc dot gnu.org
2021-12-13 11:01 ` syq at debian dot org
2021-12-13 16:25 ` ibuclaw at gdcproject dot org
2021-12-14 1:44 ` syq at debian dot org
2021-12-14 4:44 ` syq at debian dot org
2021-12-14 4:50 ` syq at debian dot org
2021-12-14 15:02 ` ibuclaw at gdcproject dot org
2021-12-14 15:06 ` ibuclaw at gdcproject dot org
2021-12-14 15:10 ` ibuclaw at gdcproject dot org
2021-12-14 15:28 ` syq at debian dot org [this message]
2021-12-14 15:58 ` ibuclaw at gdcproject dot org
2021-12-14 16:01 ` syq at debian dot org
2021-12-14 16:18 ` ibuclaw at gdcproject dot org
2021-12-15 19:01 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:16 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:17 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:17 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:19 ` ibuclaw at gdcproject dot org
2021-12-22 3:03 ` syq at debian 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-103604-4-9tDciITYvC@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).