From: Julian Waters <tanksherman27@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: Another epic optimiser failure
Date: Sun, 28 May 2023 15:50:41 +0800 [thread overview]
Message-ID: <CAP2b4GPVLBcNQdXdfS-irVpwZDxUrnGmQav_=W=_N5+xZv2FvA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Man, these clang fanboys sure are getting out of hand
I feel like all this garbage can be easily resolved by y'all showing this
idiot the exact proper options required and attaching the resulting
compiled assembly exactly as he wants it, or if gcc doesn't compile the
exact assembly he wants, explaining why gcc chose a different
route than the quote on quote "Perfect assembly" that he expects it to spit
out
And Stefan? Ever heard of the saying that "the loudest man in the room is
always the weakest"?
next reply other threads:[~2023-05-28 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 7:50 Julian Waters [this message]
2023-05-29 19:01 ` Dave Blanchard
2023-05-29 23:44 ` Nicholas Vinson
2023-05-30 4:04 ` Julian Waters
-- strict thread matches above, loose matches on Subject: below --
2023-05-27 21:04 Stefan Kanthak
2023-05-27 21:20 ` Jakub Jelinek
2023-05-27 21:28 ` Stefan Kanthak
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
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='CAP2b4GPVLBcNQdXdfS-irVpwZDxUrnGmQav_=W=_N5+xZv2FvA@mail.gmail.com' \
--to=tanksherman27@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).