From: Waldemar Brodkorb <wbx@openadk.org>
To: James Hogan <jhogan@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"Maciej W . Rozycki" <macro@mips.com>,
Matthew Fortune <matthew.fortune@mips.com>,
Florian Fainelli <florian@openwrt.org>,
Waldemar Brodkorb <wbx@openadk.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Implement __multi3 for GCC7 MIPS64r6 builds
Date: Wed, 27 Dec 2017 09:31:07 +0100 [thread overview]
Message-ID: <20171227083107.GI27558@waldemar-brodkorb.de> (raw)
In-Reply-To: <20171207072046.31125-1-jhogan@kernel.org>
Hi James,
James Hogan wrote,
> GCC7 is a bit too eager to generate suboptimal __multi3 calls (128bit
> multiply with 128bit result) for MIPS64r6 builds, even in code which
> doesn't explicitly use 128bit types, such as the following:
>
> unsigned long func(unsigned long a, unsigned long b)
> {
> return a > (~0UL) / b;
> }
>
> Which GCC rearanges to:
>
> return (unsigned __int128)a * (unsigned __int128)b > 0xffffffff;
>
> Therefore implement __multi3, but only for MIPS64r6 with GCC7 as under
> normal circumstances we wouldn't expect any calls to __multi3 to be
> generated from kernel code.
I tested the patch and it works fine for me. I can build a mips64r6
kernel and run the uClibc-ng testsuite inside qemu system emulation.
It works for me with 4.9.x and 4.14.x kernels.
Thanks
Waldemar
prev parent reply other threads:[~2017-12-27 8:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 20:55 undefined reference to `__multi3' when building with gcc 7.x Thomas Petazzoni
2017-08-04 0:05 ` Ralf Baechle
2017-08-04 15:19 ` Ralf Baechle
2017-08-04 15:41 ` Thomas Petazzoni
2017-08-04 22:25 ` Ralf Baechle
2017-08-05 11:56 ` Thomas Petazzoni
2017-08-07 8:34 ` Ralf Baechle
2017-08-13 20:46 ` Thomas Petazzoni
2017-08-17 7:15 ` Ralf Baechle
2017-08-17 8:49 ` Matthew Fortune
2017-08-17 22:19 ` Ralf Baechle
2017-10-07 19:22 ` Thomas Petazzoni
2017-11-07 17:39 ` Thomas Petazzoni
2017-08-17 1:01 ` Maciej W. Rozycki
2017-08-17 1:01 ` Maciej W. Rozycki
2017-12-03 9:56 ` Thomas Petazzoni
2017-12-05 23:49 ` James Hogan
2017-12-05 23:49 ` James Hogan
2017-12-06 7:50 ` Thomas Petazzoni
2017-12-06 7:50 ` Thomas Petazzoni
2017-12-07 7:20 ` [PATCH] MIPS: Implement __multi3 for GCC7 MIPS64r6 builds James Hogan
2017-12-08 23:52 ` Maciej W. Rozycki
2017-12-08 23:52 ` Maciej W. Rozycki
2017-12-09 7:15 ` James Hogan
2017-12-09 7:15 ` James Hogan
2017-12-27 8:31 ` Waldemar Brodkorb [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=20171227083107.GI27558@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=florian@openwrt.org \
--cc=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@mips.com \
--cc=matthew.fortune@mips.com \
--cc=ralf@linux-mips.org \
--cc=thomas.petazzoni@free-electrons.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