From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: libc-ports@sourceware.org, macro@codesourcery.com
Subject: Re: [PATCH][MIPS] clang support
Date: Mon, 06 Jun 2011 13:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1106061300320.28208@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20110604164009.GB14074@hall.aurel32.net>
On Sat, 4 Jun 2011, Aurelien Jarno wrote:
> When trying to build clang programs on MIPS, they fail as clang doesn't
> export the _MIPS_SZPTR builtin. The patch below fixes that by using
> _MIPS_SZPTR when available with a fallback on __INTPTR_WIDTH__.
Maciej, any comments on where the API for predefined macros on MIPS
(_MIPS_SIM, _MIPS_SZPTR, etc.) comes from and whether it is documented?
I'm inclined to think it's a bug in any MIPS compiler (or at least any
compiler for MIPS Linux) to fail to define these macros.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-06-06 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 16:40 Aurelien Jarno
2011-06-06 13:03 ` Joseph S. Myers [this message]
2011-06-06 13:56 ` Maciej W. Rozycki
2011-06-06 19:00 ` Aurelien Jarno
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=Pine.LNX.4.64.1106061300320.28208@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aurelien@aurel32.net \
--cc=libc-ports@sourceware.org \
--cc=macro@codesourcery.com \
/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).