public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Support calculation of pointer size for __int20__ type in _intsup.h
Date: Tue, 25 Jun 2019 17:37:00 -0000	[thread overview]
Message-ID: <20190625173732.70994.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=301facfb60db2adb8306009ac27f3b9afd08bb5e

commit 301facfb60db2adb8306009ac27f3b9afd08bb5e
Author: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Date:   Tue Jun 25 11:45:02 2019 +0100

    Support calculation of pointer size for __int20__ type in _intsup.h
    
    GCC r272640 modifies the MSP430 target to use "__int20__" for
    PTRDIFF_TYPE (and therefore INTPTR_TYPE) instead of "__int20".
    
    To support the calculation of pointer size in
    newlib/libc/include/sys/_intsup.h, definitions for __int20__ need to be
    added.

Diff:
---
 newlib/libc/include/sys/_intsup.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/newlib/libc/include/sys/_intsup.h b/newlib/libc/include/sys/_intsup.h
index 88d7400..993121b 100644
--- a/newlib/libc/include/sys/_intsup.h
+++ b/newlib/libc/include/sys/_intsup.h
@@ -37,6 +37,7 @@
 #pragma push_macro("char")
 #pragma push_macro("short")
 #pragma push_macro("__int20")
+#pragma push_macro("__int20__")
 #pragma push_macro("int")
 #pragma push_macro("long")
 #undef signed
@@ -45,12 +46,14 @@
 #undef short
 #undef int
 #undef __int20
+#undef __int20__
 #undef long
 #define signed +0
 #define unsigned +0
 #define char +0
 #define short +1
 #define __int20 +2
+#define __int20__ +2
 #define int +2
 #define long +4
 #if (__INTPTR_TYPE__ == 8 || __INTPTR_TYPE__ == 10)
@@ -189,6 +192,7 @@
 #pragma pop_macro("char")
 #pragma pop_macro("short")
 #pragma pop_macro("__int20")
+#pragma pop_macro("__int20__")
 #pragma pop_macro("int")
 #pragma pop_macro("long")


                 reply	other threads:[~2019-06-25 17:37 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=20190625173732.70994.qmail@sourceware.org \
    --to=jjohnstn@sourceware.org \
    --cc=newlib-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).