public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/79173] add-with-carry and subtract-with-borrow support (x86_64 and others) Date: Tue, 06 Jun 2023 12:01:05 +0000 [thread overview] Message-ID: <bug-79173-4-QOp1d3vwIA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-79173-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79173 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 55271 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55271&action=edit gcc14-pr79173-wip.patch Untested WIP (with backend implementation for x86 only so far). Still, need to add/tweak some peephole2s to make pr79173-{1,2,3,4}.c tests clean on both x86-64 and i?86, and then as can be seen in pr79173-5.c need to do some tweaks so that it pattern recognizes also the pattern recognized __builtin_{add,sub}_overflow instead of those being used directly. C23 is standardizing __builtin_{add,sub,mul}_overflow under the ckd_{add,sub,mul} names, so pattern recognizing it that way is definitely desirable. Oh, and maybe incrementally check what happens if one of the addends or subtrahends are immediate.
next prev parent reply other threads:[~2023-06-06 12:01 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-79173-4@http.gcc.gnu.org/bugzilla/> 2020-11-15 21:21 ` [Bug target/79173] " already5chosen at yahoo dot com 2020-11-15 21:24 ` already5chosen at yahoo dot com 2020-11-15 21:32 ` jakub at gcc dot gnu.org 2020-11-15 22:30 ` already5chosen at yahoo dot com 2020-11-15 22:45 ` already5chosen at yahoo dot com 2021-05-28 15:34 ` tkoenig at gcc dot gnu.org 2021-09-09 6:48 ` [Bug middle-end/79173] " pinskia at gcc dot gnu.org 2021-09-09 8:54 ` vincent-gcc at vinc17 dot net 2021-09-09 9:05 ` pinskia at gcc dot gnu.org 2023-06-05 7:17 ` jakub at gcc dot gnu.org 2023-06-05 13:01 ` chfast at gmail dot com 2023-06-06 12:01 ` jakub at gcc dot gnu.org [this message] 2023-06-06 16:12 ` jakub at gcc dot gnu.org 2023-06-15 7:07 ` cvs-commit at gcc dot gnu.org 2023-06-15 7:10 ` cvs-commit at gcc dot gnu.org 2023-06-15 7:16 ` cvs-commit at gcc dot gnu.org 2023-06-15 7:49 ` jakub at gcc dot gnu.org 2023-06-16 17:49 ` cvs-commit at gcc dot gnu.org 2023-06-17 15:37 ` law at gcc dot gnu.org 2023-06-17 16:34 ` jakub at gcc dot gnu.org 2023-06-20 18:18 ` cvs-commit at gcc dot gnu.org 2023-06-24 9:42 ` glisse at gcc dot gnu.org 2023-06-24 9:51 ` jakub at gcc dot gnu.org 2023-06-24 12:09 ` vincent-gcc at vinc17 dot net 2023-06-24 12:32 ` jakub at gcc dot gnu.org 2023-06-24 13:10 ` vincent-gcc at vinc17 dot net 2023-06-24 13:14 ` jakub at gcc dot gnu.org 2023-06-25 0:22 ` vincent-gcc at vinc17 dot net 2023-08-29 8:47 ` cvs-commit at gcc dot gnu.org
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-79173-4-QOp1d3vwIA@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: linkBe 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).