This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Fix recent popcount change is breaking
- From: "Bin.Cheng" <amker dot cheng at gmail dot com>
- To: Kugan <kugan dot vivekanandarajah at linaro dot org>
- Cc: Richard Guenther <richard dot guenther at gmail dot com>, Martin Liška <mliska at suse dot cz>, Andrew Pinski <pinskia at gmail dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, Jeff Law <law at redhat dot com>
- Date: Sat, 24 Nov 2018 14:38:03 +0800
- Subject: Re: [RFC] Fix recent popcount change is breaking
- References: <CAELXzTOijCYcUUuhUjvsXQMDahdYRx4RhHWGjeAAz5FiHRvW+A@mail.gmail.com> <CAFiYyc07h=+N9O5_iZFL_euup1P+8S_c2PoUpWKyH6CS4HMWWg@mail.gmail.com> <CAELXzTNwjcMUCHcXSJttNb-1beytUhwyJHCXB-GPJsqqgS9qGA@mail.gmail.com> <CA+=Sn1mPuMyRGhCHrjyQCK=sSAejFZ9A9RECGFqL3XWsQU7pTg@mail.gmail.com> <CAELXzTNN6sohuU-nmtvbXxA9x99p-9-XCtz7DjZq46jROmhgAA@mail.gmail.com> <CA+=Sn1=+YEZ1gZtehqb+5cDAf1iSZTtpDV9_znY8NKSt=MPJjw@mail.gmail.com> <CAELXzTPhmPkvnBGwkCe2sECGp-mXFOqsNyfi-Qes751CpsYbEA@mail.gmail.com> <CAFiYyc2BzqxRMV0FyZ+H_8UDhcfp6zLPjR83b5v8_2Q+nv14xg@mail.gmail.com> <b281432e-0c64-1e14-deb2-c525bb0c4c59@suse.cz> <D898DEA2-D6D5-414E-9A72-2E4357472DA5@gmail.com> <CAELXzTP4BCPCYf0Tm24G-hPFBum5q7wOKeTuYG0opL_ufgDLDw@mail.gmail.com>
On Sat, Jul 28, 2018 at 7:36 AM Kugan Vivekanandarajah
<kugan.vivekanandarajah@linaro.org> wrote:
>
> Hi,
>
> On 28 July 2018 at 01:13, Richard Biener <richard.guenther@gmail.com> wrote:
> > On July 27, 2018 3:33:59 PM GMT+02:00, "Martin Liška" <mliska@suse.cz> wrote:
> >>On 07/11/2018 02:31 PM, Richard Biener wrote:
> >>> Why not simply make popcountdi available in the kernel? They do have
> >>> implementations for other libgcc functions IIRC.
> >>
> >>Can you please Kugan create Linux kernel bug for that? So that
> >>discussion
> >>can happen?
> >
> > There's no discussion necessary, libgcc is the core compiler runtime. If you choose not to use it you have to provide your own implementation.
>
> Created a bug against kernel at
> https://bugzilla.kernel.org/show_bug.cgi?id=200671
Looks like it's concerned whether GCC would generate more inefficient
code now. If that's true, it might be better to disable this somehow
for some cases? otherwise, could someone reason about it in that
kernel bug in order to push forward a fix in kernel please?
Thanks,
bin
>
> Thanks,
> Kugan
> >
> > Richard.
> >
> >>Thanks,
> >>Martin
> >