public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: Dave Blanchard <dave@killthe.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?
Date: Mon, 5 Jun 2023 20:28:43 -0400	[thread overview]
Message-ID: <7344EE51-963F-4B7F-B948-5DEA1E8D2882@comcast.net> (raw)
In-Reply-To: <20230605190942.bf8c6a8156005dd0fa142c09@killthe.net>



> On Jun 5, 2023, at 8:09 PM, Dave Blanchard <dave@killthe.net> 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? 

Done.  Since you have not shown any ability to have a civilized conversation, I will now use my email filter to be spared any further exposure.

	paul



  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
2023-06-06  0:28         ` Paul Koning [this message]
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=7344EE51-963F-4B7F-B948-5DEA1E8D2882@comcast.net \
    --to=paulkoning@comcast.net \
    --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).