From: James Hogan <james.hogan@mips.com>
To: Antony Pavlov <antonynpavlov@gmail.com>,
Palmer Dabbelt <palmer@sifive.com>
Cc: <linux-mips@linux-mips.org>, <linux-kernel@vger.kernel.org>,
<ralf@linux-mips.org>, Matt Redfearn <matt.redfearn@mips.com>
Subject: Re: [PATCH] MIPS: use generic GCC library routines from lib/
Date: Thu, 18 Jan 2018 20:24:17 +0000 [thread overview]
Message-ID: <20180118202416.GD27409@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <57124790-F7C9-4180-AE89-A7FAA3DBDC9A@albanarts.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Thu, Jan 18, 2018 at 07:54:49PM +0000, James Hogan wrote:
> On 18 January 2018 20:05:05 GMT+00:00, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> >On Wed, 17 Jan 2018 17:34:59 -0800 (PST)
> >Palmer Dabbelt <palmer@sifive.com> wrote:
> >> Given that, I think you can also drop arch/mips/lib/libgcc.h -- if
> >it's used
> >> from anywhere else, it should be possible to use
> >include/linux/libgcc.h
> >> instead.
> >
> >I agree with you.
>
> actually theres a patch in mips-next which implements __multi3 for mips64r6, which uses that file, and in fact extends it for 128bit types.
More specifically, commit ebabcf17bcd7 ("MIPS: Implement __multi3 for
GCC7 MIPS64r6 builds"), which will find its way into v4.15. See also
https://patchwork.linux-mips.org/patch/17890/
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-18 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 6:51 [PATCH] MIPS: use generic GCC library routines from lib/ Antony Pavlov
2018-01-17 9:03 ` Matt Redfearn
2018-01-17 13:34 ` Antony Pavlov
2018-01-18 16:05 ` Palmer Dabbelt
2018-01-18 20:28 ` James Hogan
2018-01-18 16:05 ` Palmer Dabbelt
2018-01-18 1:34 ` Palmer Dabbelt
2018-01-18 20:05 ` Antony Pavlov
2018-01-18 19:54 ` James Hogan
2018-01-18 20:24 ` James Hogan [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=20180118202416.GD27409@jhogan-linux.mipstec.com \
--to=james.hogan@mips.com \
--cc=antonynpavlov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=matt.redfearn@mips.com \
--cc=palmer@sifive.com \
--cc=ralf@linux-mips.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