From: Eric Christopher <echristo@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: mips-linux-gnu doesn't use SIZE_TYPE/PTRDIFF_TYPE from mips.h
Date: Sun, 06 Oct 2002 01:02:00 -0000 [thread overview]
Message-ID: <1033886191.12860.55.camel@ghostwheel> (raw)
In-Reply-To: <orbs696o40.fsf@free.redhat.lsd.ic.unicamp.br>
On Sat, 2002-10-05 at 05:56, Alexandre Oliva wrote:
> It used to be possible to use mips-linux-gnu-gcc for
> layout-compatibility tests with mips-sgi-irix6, even for the n32 and
> n64 ABIs, but this is not possible at the moment because mips.h
> doesn't override the definitions of SIZE_TYPE and PTRDIFF_TYPE from
> svr4.h, that appears first in the tm_file list of mips*-*-linux*.
> This patch fixes this problem, such that -mabi=n32 and -mabi=64 have
> the expect effect in this toolchain, at least as far as compilation of
> a preprocessed file goes. Ok to install?
>
Yup.
-eric
--
Yuppies wear socks.
prev parent reply other threads:[~2002-10-06 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 11:13 Alexandre Oliva
2002-10-06 1:02 ` Eric Christopher [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=1033886191.12860.55.camel@ghostwheel \
--to=echristo@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.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).