From: "Stefan Kanthak" <stefan.kanthak@nexgo.de>
To: <gcc@gnu.org>, "Thomas Koenig" <tkoenig@netcologne.de>
Subject: Re: B^HDEAD code generation (AMD64)
Date: Tue, 10 Jan 2023 01:34:25 +0100 [thread overview]
Message-ID: <545B9AD08243438F810C8F68BE0CAC00@H270> (raw)
In-Reply-To: <5e02f939-7356-a43f-d570-6e270fb6ad8b@netcologne.de>
"Thomas Koenig" <tkoenig@netcologne.de> wrote:
> On 09.01.23 12:35, Stefan Kanthak wrote:
>> 20 superfluous instructions of the total 102 instructions!
>
> The proper place for bug reports is https://gcc.gnu.org/bugzilla/ .
OUCH: there's NO proper place for bugs at all!
> Feel free to submit these cases there.
I feel free to do whatever I like to do where I do it, for example:
--- bug.cpp ---
int main() {
__uint128_t long long bug = 0;
}
--- EOF ---
See <https://godbolt.org/z/G7f81Mx5Y>
regards
Stefan
next prev parent reply other threads:[~2023-01-10 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 11:35 Stefan Kanthak
2023-01-09 11:48 ` Thomas Koenig
2023-01-09 12:17 ` LIU Hao
2023-01-10 0:34 ` Stefan Kanthak [this message]
2023-01-10 3:22 ` Andrew Pinski
2023-01-10 7:12 ` Gabriel Ravier
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=545B9AD08243438F810C8F68BE0CAC00@H270 \
--to=stefan.kanthak@nexgo.de \
--cc=gcc@gnu.org \
--cc=tkoenig@netcologne.de \
/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).