From: Gabriel Ravier <gabravier@gmail.com>
To: Dave Blanchard <dave@killthe.net>, gcc@gcc.gnu.org
Subject: Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?
Date: Tue, 6 Jun 2023 02:28:27 +0200 [thread overview]
Message-ID: <7a6b6d06-d9c8-5c18-5e8a-26b8c6336dde@gmail.com> (raw)
In-Reply-To: <20230605190942.bf8c6a8156005dd0fa142c09@killthe.net>
On 6/6/23 02:09, Dave Blanchard wrote:
> On Tue, 6 Jun 2023 01:59:42 +0200
> Gabriel Ravier <gabravier@gmail.com> wrote:
>
>> [nothing of value]
> If this guy's threads are such a terrible waste of your time, how about employing your email client's filters to ignore his posts (and mine too) and fuck off?
>
> Now YOU'RE wasting everyone's time, as your type is so skilled at doing, refocusing an important discussion to generic whining about "muh feelings", instead of the real issue at hand here: GCC's optimizer is TERRIBLE!
Well, evidently you have a completely different understanding of what
the "important discussion" here is. I've simply been trying to respond
to your emails in a manner I thought appropriate: I didn't think you
were sending mails with the expectation that it is apparently
unacceptable for me to respond to them, especially when they contain
multiple explicit direct questions.
>
> I for one appreciate this guy's posts, as this issue might have never been called to my attention otherwise; certainly not if this were relegated to the dusty corner of some bug list somewhere. I've now reverted to a much older version of GCC which will hopefully waste much fewer of my old computer's CPU cycles, while also (provably) not constantly breaking my system with all the added warnings and errors every release.
I did not think Poe's law would become applicable to so many discussions
on this mailing list, but here I am... I guess that leaves me with only
one question: are you actually serious in your claim that this "much
older version of GCC" will produce faster code than a recent one ?
>
> Dave
next prev parent reply other threads:[~2023-06-06 0:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:17 Stefan Kanthak
2023-06-05 10:33 ` Jonathan Wakely
2023-06-05 11:35 ` Gabriel Ravier
2023-06-05 22:23 ` Dave Blanchard
2023-06-05 23:59 ` Gabriel Ravier
2023-06-06 0:09 ` Dave Blanchard
2023-06-06 0:28 ` Gabriel Ravier [this message]
2023-06-06 0:28 ` Paul Koning
2023-06-06 7:57 ` Jonathan Wakely
2023-06-06 8:31 ` David Brown
2023-06-05 12:55 Julian Waters
2023-06-06 8:36 Julian Waters
2023-06-06 12:53 ` Paul Smith
2023-06-06 15:37 ` David Brown
2023-06-06 17:39 ` David Edelsohn
2023-06-06 18:43 ` Arsen Arsenović
2023-06-08 11:36 ` Mark Wielaard
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=7a6b6d06-d9c8-5c18-5e8a-26b8c6336dde@gmail.com \
--to=gabravier@gmail.com \
--cc=dave@killthe.net \
--cc=gcc@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: 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).