public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102974] GCC optimization is very poor for add carry and multiplication combos
Date: Wed, 27 Oct 2021 21:22:31 +0000	[thread overview]
Message-ID: <bug-102974-4-X0PObGc6Pt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102974-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102974

--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #2)
> There might be another bug about _addcarryx_u64 already.

This is 32 bit addcarry.

  parent reply	other threads:[~2021-10-27 21:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 21:17 [Bug tree-optimization/102974] New: " unlvsur at live dot com
2021-10-27 21:18 ` [Bug tree-optimization/102974] " pinskia at gcc dot gnu.org
2021-10-27 21:19 ` [Bug target/102974] " pinskia at gcc dot gnu.org
2021-10-27 21:22 ` unlvsur at live dot com [this message]
2021-10-27 21:23 ` unlvsur at live dot com
2021-10-27 21:24 ` pinskia at gcc dot gnu.org
2021-10-27 22:39 ` unlvsur at live dot com
2021-10-27 23:02 ` unlvsur at live dot com
2021-10-28  8:20 ` rguenth at gcc dot gnu.org
2021-10-28  9:56 ` unlvsur at live dot com
2021-11-01 10:07 ` marxin at gcc dot gnu.org
2023-06-03 23:53 ` slash.tmp at free dot fr
2023-06-06  6:56 ` slash.tmp at free dot fr
2023-06-06  7:01 ` unlvsur at live dot com
2023-06-06  7:02 ` unlvsur at live dot com
2023-06-06  7:05 ` unlvsur at live dot com
2023-06-06 17:19 ` slash.tmp at free dot fr

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=bug-102974-4-X0PObGc6Pt@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).