public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com>
To: "Martin Liška" <mliska@suse.cz>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "macro@embecosm.com" <macro@embecosm.com>,
	Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
	"joseph@codesourcery.com" <joseph@codesourcery.com>
Subject: Re: [PATCH] libsanitizer: Cherry-pick 2bfb0fcb51510f22723c8cdfefe from upstream
Date: Fri, 29 Jul 2022 06:38:37 +0000	[thread overview]
Message-ID: <AM0PR03MB488253F558C35F62A90355F182999@AM0PR03MB4882.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <c9c9616c-7f66-e937-15a6-92fab64f2a5f@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

Thanks Martin! I'm sending out the output from git format-patch as an attachment to this email.


From: Martin Liška <mliska@suse.cz>
Sent: Thursday, July 28, 2022 3:48 PM
To: Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com>; gcc-patches@gcc.gnu.org <gcc-patches@gcc.gnu.org>
Cc: macro@embecosm.com <macro@embecosm.com>; Djordje Todorovic <Djordje.Todorovic@syrmia.com>; joseph@codesourcery.com <joseph@codesourcery.com>
Subject: Re: [PATCH] libsanitizer: Cherry-pick 2bfb0fcb51510f22723c8cdfefe from upstream 
 
On 7/28/22 15:43, Dimitrije Milosevic wrote:
> |Gentle ping, requiring someone to push the change. :)|

Sure, I can do that, but please attach output of (git format-patch) as an attachment
to an email. The current email has a weird format I can directly apply with git am.

Cheers,
Martin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-libsanitizer-Cherry-pick-2bfb0fcb51510f22723c8cdfefe.patch --]
[-- Type: text/x-patch; name="0001-libsanitizer-Cherry-pick-2bfb0fcb51510f22723c8cdfefe.patch", Size: 1599 bytes --]

From 9d7646428bf36449cde380230bcc20fa835857dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dimitrije=20Milo=C5=A1evi=C4=87?=
 <dimitrije.milosevic@syrmia.com>
Date: Fri, 29 Jul 2022 08:36:06 +0200
Subject: [PATCH] libsanitizer: Cherry-pick 2bfb0fcb51510f22723c8cdfefe from
 upstream

2bfb0fcb51510f22723c8cdfefe [Sanitizer][MIPS] Fix stat struct size for the O32 ABI.

Signed-off-by: Dimitrije Milosevic <dimitrije.milosevic@syrmia.com>.

---
 .../sanitizer_common/sanitizer_platform_limits_posix.h     | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
index 89772a7e5c0..75c6cc7f285 100644
--- a/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
+++ b/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h
@@ -81,9 +81,10 @@ const unsigned struct_kernel_stat64_sz = 104;
 const unsigned struct_kernel_stat_sz = 144;
 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);
+const unsigned struct_kernel_stat_sz =
+    SANITIZER_ANDROID
+        ? FIRST_32_SECOND_64(104, 128)
+        : FIRST_32_SECOND_64((_MIPS_SIM == _ABIN32) ? 160 : 144, 216);
 const unsigned struct_kernel_stat64_sz = 104;
 #elif defined(__s390__) && !defined(__s390x__)
 const unsigned struct_kernel_stat_sz = 64;
-- 
2.25.1


  reply	other threads:[~2022-07-29  6:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  6:55 Dimitrije Milosevic
2022-07-25  7:04 ` Xi Ruoyao
2022-07-27  6:41 ` PING: " Dimitrije Milosevic
2022-07-27  6:43   ` Xi Ruoyao
2022-07-27  6:52     ` Dimitrije Milosevic
2022-07-27 12:57       ` Richard Sandiford
2022-07-28 13:43 ` Dimitrije Milosevic
2022-07-28 13:48   ` Martin Liška
2022-07-29  6:38     ` Dimitrije Milosevic [this message]
2022-08-01  4:11       ` Martin Liška

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=AM0PR03MB488253F558C35F62A90355F182999@AM0PR03MB4882.eurprd03.prod.outlook.com \
    --to=dimitrije.milosevic@syrmia.com \
    --cc=Djordje.Todorovic@syrmia.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=macro@embecosm.com \
    --cc=mliska@suse.cz \
    /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).