From: David Brown <david@westcontrol.com>
To: gcc@gcc.gnu.org
Subject: Re: Will GCC eventually support SSE2 or SSE4.1?
Date: Fri, 26 May 2023 18:44:41 +0200 [thread overview]
Message-ID: <u4qnlp$uur$1@ciao.gmane.io> (raw)
In-Reply-To: <24C17D6B62D041D39D3962704D1B4B67@H270>
On 26/05/2023 17:49, Stefan Kanthak wrote:
> I don't like to argue with idiots: they beat me with experience!
>
> Stefan
>
Stefan, you are clearly not happy about the /free/ compiler you are
using, and its /free/ documentation (which, despite its flaws, is better
than I have seen for most other compilers).
Instead of filing a bug report, as you have been asked to do, or reading
the documentation, or thinking, or posting to an appropriate mailing
list, you have chosen to rant, yell, shout at and insult the very people
who could make the changes and improvements you want.
So who, exactly, do you think is acting like an idiot? I'd say it is
the rude and arrogant fool that is sawing off the branch he is sitting on.
Remember, these are people with /no/ obligation to help you. Some do
gcc development as voluntary contributions, others are paid to work on
it - but they are not paid by /you/. And none are paid to sit and
listen to your tantrums.
So if you want to shout and rant and blow off steam, go make a tweet or
something. If you actually hope to see gcc change its optimisation,
flag details or documentation to your liking, then your current
behaviour is the worst possible tactic. So let your final post to this
thread be an apology, then register bug reports with what you see as
bugs or scope for improvement in the project. Please - for the sanaity
of the gcc developers and for the benefit of gcc users everywhere - stop
your aggravating posts here, so that Jonathan and the others can back to
what they do best - improving gcc for everyone.
David
next prev parent reply other threads:[~2023-05-26 16:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:46 Stefan Kanthak
2023-05-26 7:00 ` Andrew Pinski
2023-05-26 7:30 ` Jonathan Wakely
2023-05-26 7:58 ` Stefan Kanthak
2023-05-26 8:16 ` Sam James
2023-05-26 8:28 ` Jonathan Wakely
2023-05-26 8:59 ` Stefan Kanthak
2023-05-26 9:22 ` Jakub Jelinek
2023-05-26 11:28 ` Stefan Kanthak
2023-05-26 11:42 ` Jonathan Wakely
2023-05-26 12:03 ` Stefan Kanthak
2023-05-26 12:16 ` Jonathan Wakely
2023-05-26 12:22 ` Stefan Kanthak
2023-05-26 13:00 ` Mark Wielaard
2023-05-26 12:23 ` Jonathan Wakely
2023-05-26 11:36 ` Stefan Kanthak
2023-05-26 11:45 ` Jonathan Wakely
2023-05-26 12:19 ` Stefan Kanthak
2023-05-26 12:30 ` Jonathan Wakely
2023-05-26 12:42 ` Stefan Kanthak
2023-05-26 13:33 ` Nicholas Vinson
2023-05-26 12:37 ` Jakub Jelinek
2023-05-26 13:49 ` Stefan Kanthak
2023-05-26 14:07 ` Jonathan Wakely
2023-05-26 14:18 ` Jakub Jelinek
2023-05-26 14:41 ` Stefan Kanthak
2023-05-26 14:55 ` Jonathan Wakely
2023-05-26 15:07 ` Stefan Kanthak
2023-05-26 14:26 ` Stefan Kanthak
2023-05-26 14:58 ` Jonathan Wakely
2023-05-26 15:49 ` Stefan Kanthak
2023-05-26 16:44 ` David Brown [this message]
2023-05-27 18:16 ` Will GCC eventually support correct code compilation? Dave Blanchard
2023-05-27 18:59 ` Jason Merrill
2023-05-28 11:50 ` David Brown
2023-05-26 9:22 ` Will GCC eventually support SSE2 or SSE4.1? Jonathan Wakely
2023-05-26 8:12 ` Hagen Paul Pfeifer
2023-05-26 9:51 ` Jonathan Wakely
2023-05-26 11:34 ` Nicholas Vinson
2023-05-26 15:10 ` LIU Hao
2023-05-26 15:40 ` Stefan Kanthak
2023-05-27 18:20 ` LIU Hao
2023-05-27 18:49 ` Stefan Kanthak
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='u4qnlp$uur$1@ciao.gmane.io' \
--to=david@westcontrol.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).