From: Paul Smith <paul@mad-scientist.net>
To: Julian Waters <tanksherman27@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?
Date: Tue, 06 Jun 2023 08:53:31 -0400 [thread overview]
Message-ID: <386a1d9c18eb7af15eef409c36a196ec0f99ad22.camel@mad-scientist.net> (raw)
In-Reply-To: <CAP2b4GO8H3bmWi-UPejmH6aFfyTArCucupvymxvuVpZ+5puh=A@mail.gmail.com>
On Tue, 2023-06-06 at 16:36 +0800, Julian Waters via Gcc wrote:
> Sorry for my outburst, to the rest of this list. I can no longer stay
> silent and watch these little shits bully people who are too kind to
> fire back with the same kind of venom in their words.
Many of us have had Dave in our killfiles for a long time already. I
recommend you (and everyone else) do the same. You won't miss out on
any information of any use to anyone: he apparently just enjoys making
other people angry.
I'm quite serious: it's so not worth the mental energy to even read his
messages, much less to reply to him. Arguing with "people who are
wrong on the internet" can be cathartic but this is not arguing, it's
just stabbing yourself in the eye with a pencil. Don't play.
next prev parent reply other threads:[~2023-06-06 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:36 Julian Waters
2023-06-06 12:53 ` Paul Smith [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 12:55 Julian Waters
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
2023-06-06 0:28 ` Paul Koning
2023-06-06 7:57 ` Jonathan Wakely
2023-06-06 8:31 ` David Brown
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=386a1d9c18eb7af15eef409c36a196ec0f99ad22.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=gcc@gcc.gnu.org \
--cc=tanksherman27@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).