From: Christian Borntraeger <borntraeger@de.ibm.com>
To: linux-sparse@vger.kernel.org
Cc: linux-s390@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [PATCH] s390x: add the proper defines for data types
Date: Thu, 22 Jan 2015 10:51:50 +0100 [thread overview]
Message-ID: <1421920310-1499-1-git-send-email-borntraeger@de.ibm.com> (raw)
This patch fixes several issues when compiling code under s390x
(64bit) with cgcc, e.g.
/usr/include/gnu/stubs.h:8:12: error: unable to open 'gnu/stubs-32.h'
by providing the proper defines.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
cgcc | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/cgcc b/cgcc
index 8e38174..d7b1c99 100755
--- a/cgcc
+++ b/cgcc
@@ -279,6 +279,12 @@ sub add_specs {
&float_types (1, 1, 21, [24,8], [53,11], [113,15]) .
&define_size_t ($m64 ? "long unsigned int" : "unsigned int") .
' -D__SIZEOF_POINTER__=' . ($m64 ? '8' : '4'));
+ } elsif ($spec eq 's390x') {
+ return (' -D__s390x__ -D__s390__ -D_BIG_ENDIAN' .
+ &integer_types (8, 16, 32, $m64 ? 64 : 32, 64) .
+ &float_types (1, 1, 36, [24,8], [53,11], [113,15]) .
+ &define_size_t ("long unsigned int") .
+ ' -D__SIZEOF_POINTER__=' . ($m64 ? '8' : '4'));
} elsif ($spec eq 'host_os_specs') {
my $os = `uname -s`;
chomp $os;
@@ -294,6 +300,8 @@ sub add_specs {
return &add_specs ('x86_64');
} elsif ($arch =~ /^(ppc)$/i) {
return &add_specs ('ppc');
+ } elsif ($arch =~ /^(s390x)$/i) {
+ return &add_specs ('s390x');
} elsif ($arch =~ /^(sparc64)$/i) {
return &add_specs ('sparc64');
}
--
1.7.1
next reply other threads:[~2015-01-22 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:51 Christian Borntraeger [this message]
2015-01-22 13:50 ` [PATCH] s390x: add the proper defines for data types (sparse) Christian Borntraeger
2015-01-22 17:52 ` [PATCH] s390x: add the proper defines for data types Christopher Li
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=1421920310-1499-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).