public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105253] __popcountdi2 calls generated in kernel code with gcc12 Date: Wed, 13 Apr 2022 10:01:33 +0000 [thread overview] Message-ID: <bug-105253-4-1Zav5zeTGR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105253-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105253 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This is a regression (as in we don't want such a call in that case for performance reasons and in the past we didn't emit it).
next prev parent reply other threads:[~2022-04-13 10:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 5:28 [Bug c/105253] New: " raj.khem at gmail dot com 2022-04-13 5:37 ` [Bug middle-end/105253] " pinskia at gcc dot gnu.org 2022-04-13 5:40 ` pinskia at gcc dot gnu.org 2022-04-13 5:47 ` raj.khem at gmail dot com 2022-04-13 6:40 ` pinskia at gcc dot gnu.org 2022-04-13 7:00 ` rguenth at gcc dot gnu.org 2022-04-13 8:52 ` jakub at gcc dot gnu.org 2022-04-13 9:15 ` rguenth at gcc dot gnu.org 2022-04-13 9:27 ` jakub at gcc dot gnu.org 2022-04-13 9:39 ` jakub at gcc dot gnu.org 2022-04-13 9:52 ` jakub at gcc dot gnu.org 2022-04-13 10:01 ` jakub at gcc dot gnu.org [this message] 2022-04-13 10:02 ` jakub at gcc dot gnu.org 2022-04-13 12:22 ` rguenth at gcc dot gnu.org 2022-04-13 12:31 ` rguenth at gcc dot gnu.org 2022-04-13 13:45 ` cvs-commit at gcc dot gnu.org 2022-04-13 13:46 ` jakub at gcc dot gnu.org 2022-04-15 7:48 ` crazylht at gmail dot com
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=bug-105253-4-1Zav5zeTGR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).