unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Portability bug with UINTPTR_MAX in Solaris/Forte
Date: Sat, 21 Jun 2003 11:20:16 +1000	[thread overview]
Message-ID: <87isr0cjlb.fsf@zip.com.au> (raw)
In-Reply-To: <uw5vfv3sxzo.fsf@saturn.math.uni-magdeburg.de> (Matthias Koeppe's message of "Wed, 18 Jun 2003 08:25:47 +0200")

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

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?


[-- Attachment #2: tags.h.solaris-uintptr.diff --]
[-- Type: text/plain, Size: 564 bytes --]

--- tags.h.~1.103.~	2003-06-12 10:58:55.000000000 +1000
+++ tags.h	2003-06-21 11:19:56.000000000 +1000
@@ -49,7 +49,9 @@
 #define SCM_T_SIGNED_BITS_MIN LONG_MIN
 #endif
 
-#if SCM_SIZEOF_UINTPTR_T != 0 && defined(UINTPTR_MAX)
+/* On solaris 7 and 8, Sun workshop cc has UINTPTR_MAX defined to empty.  To
+   avoid uintptr_t in this case we require UINTPTR_MAX-0 != 0.  */
+#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

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

  reply	other threads:[~2003-06-21  1:20 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 [this message]
2003-06-23  9:15   ` Matthias Koeppe
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=87isr0cjlb.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-devel@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).