From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH] Define wordsize.h macros everywhere
Date: Thu, 10 Nov 2016 15:43:00 -0000 [thread overview]
Message-ID: <1478792562.4630.74.camel@caviumnetworks.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611101427420.26763@digraph.polyomino.org.uk>
On Thu, 2016-11-10 at 14:28 +0000, Joseph Myers wrote:
> I see errors in tilepro-linux-gnu builds with this patch:
>
> ../sysdeps/generic/stdint.h:252:7: error: "__WORDSIZE32_PTRDIFF_LONG"
> is not defined [-Werror=undef]
> Â #Â Â if __WORDSIZE32_PTRDIFF_LONG
> Â Â Â Â Â Â Â ^~~~~~~~~~~~~~~~~~~~~~~~~
> ../sysdeps/generic/stdint.h:269:7: error: "__WORDSIZE32_SIZE_ULONG"
> is not defined [-Werror=undef]
> Â #Â Â if __WORDSIZE32_SIZE_ULONG
> Â Â Â Â Â Â Â ^~~~~~~~~~~~~~~~~~~~~~~
>
Sorry about that, I am not sure how those were missed. Â I will check in
this patch as the obvious fix.
Steve Ellcey
sellcey@caviumnetworks.com
2016-11-10  Steve Ellcey  <sellcey@caviumnetworks.com>
* sysdeps/tile/tilepro/bits/wordsize.h: Define __WORDSIZE32_SIZE_ULONG
and __WORDSIZE32_PTRDIFF_LONG.
diff --git a/sysdeps/tile/tilepro/bits/wordsize.h b/sysdeps/tile/tilepro/bits/wo
rdsize.h
index 8281538..d2c4a35 100644
--- a/sysdeps/tile/tilepro/bits/wordsize.h
+++ b/sysdeps/tile/tilepro/bits/wordsize.h
@@ -2,3 +2,5 @@
Â
 #define __WORDSIZE 32
 #define __WORDSIZE_TIME64_COMPAT32 0
+#define __WORDSIZE32_SIZE_ULONG 0
+#define __WORDSIZE32_PTRDIFF_LONG 0
prev parent reply other threads:[~2016-11-10 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 18:34 Steve Ellcey
2016-10-26 19:39 ` Steve Ellcey
2016-10-26 20:07 ` Joseph Myers
2016-10-27 18:45 ` Steve Ellcey
2016-10-27 20:16 ` Adhemerval Zanella
2016-10-28 16:07 ` Steve Ellcey
2016-11-03 20:41 ` Steve Ellcey
2016-11-04 8:16 ` Andreas Schwab
2016-11-10 14:28 ` Joseph Myers
2016-11-10 15:43 ` Steve Ellcey [this message]
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=1478792562.4630.74.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).