From: Aurelien Jarno <aurelien@aurel32.net>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, libc-ports@sourceware.org
Subject: Re: [PATCH][MIPS] clang support
Date: Mon, 06 Jun 2011 19:00:00 -0000 [thread overview]
Message-ID: <20110606190004.GB3601@hall.aurel32.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1106061446420.1833@tp.orcam.me.uk>
On Mon, Jun 06, 2011 at 02:55:36PM +0100, Maciej W. Rozycki wrote:
> On Mon, 6 Jun 2011, Joseph S. Myers 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?
>
> This was originally defined by SGI. One documentary reference I have is:
> "MIPSpro(TM) Compiling and Performance Tuning Guide" SGI's document
> #007-2360-008.
>
> > 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.
>
> I agree. Any Linux userland C code specifically crafted for a MIPS
> processor will assume these macros are available. Note that some of them
> are defined by <sgidefs.h> rather than the compiler itself (the API is
> somewhat odd).
>
Thanks for the details. It is now clear to me that it has to be fixed,
the clang side.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2011-06-06 19:00 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
2011-06-06 13:56 ` Maciej W. Rozycki
2011-06-06 19:00 ` Aurelien Jarno [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=20110606190004.GB3601@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=joseph@codesourcery.com \
--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).