From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Subject: Re: Portability bug with UINTPTR_MAX in Solaris/Forte
Date: Mon, 23 Jun 2003 11:15:27 +0200 [thread overview]
Message-ID: <uw5of0prw7k.fsf@saturn.math.uni-magdeburg.de> (raw)
In-Reply-To: <87isr0cjlb.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 21 Jun 2003 11:20:16 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Matthias Koeppe <mkoeppe@merkur.math.uni-magdeburg.de> writes:
>>
>> On Solaris, there is a uintptr_t, and UINTPTR_MAX is also a defined
>> macro, but it expands to nothing.
>
> Literally nothing? Perhaps the change below would do the trick.
> Does the same apply to INTPTR_MAX?
Thanks, your trick does the change. (I still think that tricky
things like this should be checked at `configure' time, rather than
during compilation, though.)
The same does not apply to the signed version because INTPTR_MIN is
not defined at all. I have updated your patch to check this anyway,
for "completeness".
--- tags.h.~1.103.~ Mon Jun 16 16:50:07 2003
+++ tags.h Mon Jun 23 11:13:09 2003
@@ -39,7 +39,11 @@
/* In the beginning was the Word:
*/
-#if SCM_SIZEOF_INTPTR_T != 0 && defined(INTPTR_MAX) && defined(INTPTR_MIN)
+/* On Solaris 7 and 8, /usr/include/sys/int_limits.h defines
+ INTPTR_MAX and UINTPTR_MAX to empty, INTPTR_MIN is not defined.
+ To avoid uintptr_t and intptr_t in this case we require
+ UINTPTR_MAX-0 != 0 etc. */
+#if SCM_SIZEOF_INTPTR_T != 0 && defined(INTPTR_MAX) && defined(INTPTR_MIN) && INTPTR_MAX-0 != 0 && INTPTR_MIN-0 != 0
typedef intptr_t scm_t_signed_bits;
#define SCM_T_SIGNED_BITS_MAX INTPTR_MAX
#define SCM_T_SIGNED_BITS_MIN INTPTR_MIN
@@ -49,7 +53,7 @@
#define SCM_T_SIGNED_BITS_MIN LONG_MIN
#endif
-#if SCM_SIZEOF_UINTPTR_T != 0 && defined(UINTPTR_MAX)
+#if SCM_SIZEOF_UINTPTR_T != 0 && defined(UINTPTR_MAX) && UINTPTR_MAX-0 != 0
typedef uintptr_t scm_t_bits;
#define SIZEOF_SCM_T_BITS SCM_SIZEOF_UINTPTR_T
#define SCM_T_BITS_MAX UINTPTR_MAX
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-23 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 6:25 Portability bug with UINTPTR_MAX in Solaris/Forte Matthias Koeppe
2003-06-21 1:20 ` Kevin Ryde
2003-06-23 9:15 ` Matthias Koeppe [this message]
2003-06-23 23:05 ` Kevin Ryde
2003-06-25 15:17 ` Matthias Koeppe
2003-07-05 0:03 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uw5of0prw7k.fsf@saturn.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
/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).