public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Julian Waters <tanksherman27@gmail.com>
To: gabravier@gmail.com, 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 16:36:36 +0800	[thread overview]
Message-ID: <CAP2b4GO8H3bmWi-UPejmH6aFfyTArCucupvymxvuVpZ+5puh=A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

It's alright Gabriel, pay this intellectually challenged individual no
mind. It's clear that, unlike Stefan, who at the very least knows how to
disassemble native code and understands what the instruction sequences mean
(even though the way he goes about it is flat out wrong), this retard
doesn't know how the fuck compiler code emission works in the slightest.
I'd be surprised if our friend Dave here (from "killthe.net", VERY
professional Dave!) even knows what registers or the stack are. Hell Dave,
forget about something as advanced as a compiler for native chip
architectures, do you even know the basic design principles of a fucking
Interpreter? Should be easy for a "Big Dog" like you, shouldn't it? Hell,
I'll make it easy for you, you can ignore ultra low level Interpreters like
the one within the JVM (because there is no fucking way in hell someone
like you with IQ comparable to room temperature can ever grasp how such a
complex system works), how would a basic Interpreter even function? How
does simple interpreter dispatch work, hm? How does cpython (or PyPy) or
even one as simple as the Matz Ruby Interpreter operate? Can you answer
that Dave? Or have you deluded your braindead self into thinking that
you're one of the "Big Dogs" (Your own words) and are now punching way
above your league? Are you going to answer with the "Hurr durr they work by
translating source code to machine code on the fly" that outdated and flat
out wrong as shit text in computer science textbooks say? Pffft



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. They may be polite enough
to refrain from doing so, Dave, but rest assured, I am far from as kind as
they are when dealing with assholes. I'm all for constructive criticism to
help improve a product as a whole, but if any of Stefan's (or god forbid,
David's) mails are "constructive", then Donald Trump is the second fucking
incarnation of Jesus Christ himself returning to earth for the second coming

             reply	other threads:[~2023-06-06  8:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  8:36 Julian Waters [this message]
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
  -- 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='CAP2b4GO8H3bmWi-UPejmH6aFfyTArCucupvymxvuVpZ+5puh=A@mail.gmail.com' \
    --to=tanksherman27@gmail.com \
    --cc=gabravier@gmail.com \
    --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).