From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Andrew Pinski <andrew.pinski@caviumnetworks.com>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] Have MIPS64/n64 imply wordsize-64
Date: Sat, 14 Apr 2012 21:35:00 -0000 [thread overview]
Message-ID: <CADZpyiwKV+sjVnRs10ipwqZfT_KwqUKHTPQnCbaPjc0qqB9YUA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1nd19i9ZT0UeuLoU69r_Fa1QKbX-p5qzBD3KBCMUtsNGw@mail.gmail.com>
On Fri, Apr 13, 2012 at 11:00 PM, Andrew Pinski
<andrew.pinski@caviumnetworks.com> wrote:
>>> OK? Note I don't have write access yet.
>>
>> Ignore this patch, it does not work. For some reason I thought I
>> tested it but I must have messed up.
>
> It turns out this was already discussed before
> http://sourceware.org/ml/libc-ports/2008-12/msg00007.html .
It might be interesting to see how the generic code can be adjusted to
try support MIPS, and thus reduce the duplication. I don't know how
hard or worthwhile that might be.
Cheers,
Carlos.
prev parent reply other threads:[~2012-04-14 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 1:21 Andrew Pinski
2012-04-14 2:11 ` Andrew Pinski
2012-04-14 3:00 ` Andrew Pinski
2012-04-14 21:35 ` Carlos O'Donell [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=CADZpyiwKV+sjVnRs10ipwqZfT_KwqUKHTPQnCbaPjc0qqB9YUA@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=andrew.pinski@caviumnetworks.com \
--cc=libc-ports@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).