From: "Stefan Kanthak" <stefan.kanthak@nexgo.de>
To: "Jakub Jelinek" <jakub@redhat.com>
Cc: <gcc@gnu.org>
Subject: Re: Another epic optimiser failure
Date: Sat, 27 May 2023 23:28:24 +0200 [thread overview]
Message-ID: <3E52AE4B49614D19BDC50FC79B8653F3@H270> (raw)
In-Reply-To: <ZHJ0MxuFxFDZVvKx@tucnak>
"Jakub Jelinek" <jakub@redhat.com> wrote, completely clueless:
> On Sat, May 27, 2023 at 11:04:11PM +0200, Stefan Kanthak wrote:
>> OUCH: popcnt writes the WHOLE result register, there is ABSOLUTELY
>> no need to clear it beforehand nor to clear the higher 24 bits
>> afterwards!
>
> Except that there is. See https://gcc.gnu.org/PR62011 for details.
GUESS WHY I EXPLICITLY WROTE
| JFTR: before GCC zealots write nonsense: see -march= or -mtune=
NOT AMUSED ABOUT YOUR CRYING INCOMPETENCE!
Stefan
next prev parent reply other threads:[~2023-05-27 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 21:04 Stefan Kanthak
2023-05-27 21:20 ` Jakub Jelinek
2023-05-27 21:28 ` Stefan Kanthak [this message]
2023-05-27 21:42 ` Andrew Pinski
2023-05-27 22:00 ` Stefan Kanthak
2023-05-27 22:46 ` Jonathan Wakely
2023-05-28 6:28 ` Nicholas Vinson
2023-05-28 7:50 Julian Waters
2023-05-29 19:01 ` Dave Blanchard
2023-05-29 23:44 ` Nicholas Vinson
2023-05-30 4:04 ` Julian Waters
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=3E52AE4B49614D19BDC50FC79B8653F3@H270 \
--to=stefan.kanthak@nexgo.de \
--cc=gcc@gnu.org \
--cc=jakub@redhat.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).