public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/release/2.38/master] sparc: Remove 64 bit check on sparc32 wordsize (BZ 27574)
Date: Tue, 23 Apr 2024 19:20:30 +0000 (GMT)	[thread overview]
Message-ID: <20240423192030.5822C384AB65@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=61484011e76d2bfafbe401f7058717c2029dd155

commit 61484011e76d2bfafbe401f7058717c2029dd155
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Wed Jan 17 10:13:06 2024 -0300

    sparc: Remove 64 bit check on sparc32 wordsize (BZ 27574)
    
    The sparc32 is always 32 bits.
    
    Checked on sparcv9-linux-gnu.
    
    (cherry picked from commit dd57f5e7b652772499cb220d78157c1038d24f06)

Diff:
---
 sysdeps/sparc/sparc32/bits/wordsize.h | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/sysdeps/sparc/sparc32/bits/wordsize.h b/sysdeps/sparc/sparc32/bits/wordsize.h
index 2f66f10d72..4bbd2e63b4 100644
--- a/sysdeps/sparc/sparc32/bits/wordsize.h
+++ b/sysdeps/sparc/sparc32/bits/wordsize.h
@@ -1,11 +1,6 @@
 /* Determine the wordsize from the preprocessor defines.  */
 
-#if defined __arch64__ || defined __sparcv9
-# define __WORDSIZE	64
-# define __WORDSIZE_TIME64_COMPAT32	1
-#else
-# define __WORDSIZE	32
-# define __WORDSIZE_TIME64_COMPAT32	0
-# define __WORDSIZE32_SIZE_ULONG	0
-# define __WORDSIZE32_PTRDIFF_LONG	0
-#endif
+#define __WORDSIZE	32
+#define __WORDSIZE_TIME64_COMPAT32	0
+#define __WORDSIZE32_SIZE_ULONG	0
+#define __WORDSIZE32_PTRDIFF_LONG	0

                 reply	other threads:[~2024-04-23 19:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240423192030.5822C384AB65@sourceware.org \
    --to=fw@sourceware.org \
    --cc=glibc-cvs@sourceware.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).