From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Kugan <kugan.vivekanandarajah@linaro.org>
Cc: "Richard Guenther" <richard.guenther@gmail.com>,
"Martin Liška" <mliska@suse.cz>,
"Andrew Pinski" <pinskia@gmail.com>,
"gcc-patches List" <gcc-patches@gcc.gnu.org>,
"Jeff Law" <law@redhat.com>
Subject: Re: [RFC] Fix recent popcount change is breaking
Date: Sat, 24 Nov 2018 06:38:00 -0000 [thread overview]
Message-ID: <CAHFci2-LtEkMtYOv2sR6wnBjWopwrVLPBrw8n4jLhGP=OHGqSQ@mail.gmail.com> (raw)
In-Reply-To: <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
> >
prev parent reply other threads:[~2018-11-24 6:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 13:06 Kugan Vivekanandarajah
2018-07-10 13:18 ` Richard Biener
2018-07-10 13:27 ` Jakub Jelinek
2018-07-10 13:34 ` Richard Biener
2018-07-10 14:44 ` Jeff Law
2018-07-10 14:42 ` Jeff Law
2018-07-11 1:13 ` Kugan Vivekanandarajah
2018-07-11 1:19 ` Andrew Pinski
2018-07-11 1:35 ` Kugan Vivekanandarajah
2018-07-11 5:43 ` Andrew Pinski
2018-07-11 11:26 ` Kugan Vivekanandarajah
2018-07-11 12:31 ` Richard Biener
2018-07-27 13:34 ` Martin Liška
2018-07-27 15:14 ` Richard Biener
2018-07-27 23:36 ` Kugan Vivekanandarajah
2018-11-24 6:38 ` Bin.Cheng [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='CAHFci2-LtEkMtYOv2sR6wnBjWopwrVLPBrw8n4jLhGP=OHGqSQ@mail.gmail.com' \
--to=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.org \
--cc=law@redhat.com \
--cc=mliska@suse.cz \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).