From: Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com>
To: Xi Ruoyao <xry111@xry111.site>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: Mips: Fix kernel_stat structure size
Date: Fri, 1 Jul 2022 14:25:50 +0000 [thread overview]
Message-ID: <AM0PR03MB4882E85892DDAD14D36A1BA382BD9@AM0PR03MB4882.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <a3e2868e6cdd5681f1064c7c76621ef973a1bd77.camel@xry111.site>
Thanks Xi. Forgive me as I'm not that familiar with the coding standards
when submitting patches for a review.
Here is the updated version of the patch.
Fix kernel_stat structure size for non-Android 32-bit Mips.
LLVM currently has this value for the kernel_stat structure size,
as per compiler-rt/lib/sanitizer-common/sanitizer_platform_limits_posix.h.
This also resolves one of the build issues for non-Android 32-bit Mips.
libsanitizer/ChangeLog:
* sanitizer_common/sanitizer_platform_limits_posix.h: Fix
kernel_stat structure size for non-Android 32-bit Mips.
---
libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
index 89772a7e5c0..62a99035db3 100644
--- a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
+++ b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
@@ -83,7 +83,7 @@ const unsigned struct_kernel_stat64_sz = 104;
#elif defined(__mips__)
const unsigned struct_kernel_stat_sz = SANITIZER_ANDROID
? FIRST_32_SECOND_64(104, 128)
- : FIRST_32_SECOND_64(144, 216);
+ : FIRST_32_SECOND_64(160, 216);
const unsigned struct_kernel_stat64_sz = 104;
#elif defined(__s390__) && !defined(__s390x__)
const unsigned struct_kernel_stat_sz = 64;
---
next prev parent reply other threads:[~2022-07-01 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 12:40 Dimitrije Milosevic
2022-07-01 12:54 ` Xi Ruoyao
2022-07-01 14:25 ` Dimitrije Milosevic [this message]
2022-07-06 11:34 ` Dimitrije Milosevic
2022-07-09 1:42 ` Hans-Peter Nilsson
2022-07-09 1:49 ` Xi Ruoyao
2022-07-09 14:44 ` Hans-Peter Nilsson
2022-07-12 6:42 ` Dimitrije Milosevic
2022-07-12 16:44 ` Hans-Peter Nilsson
2022-07-13 1:21 ` Xi Ruoyao
2022-07-13 2:38 ` Xi Ruoyao
2022-07-14 11:04 ` Dimitrije Milosevic
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=AM0PR03MB4882E85892DDAD14D36A1BA382BD9@AM0PR03MB4882.eurprd03.prod.outlook.com \
--to=dimitrije.milosevic@syrmia.com \
--cc=Djordje.Todorovic@syrmia.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=xry111@xry111.site \
/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).