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 c++/110304] __builtin_adcs missing and jakub you miss the point of builtin_adcb Date: Tue, 20 Jun 2023 19:48:51 +0000 [thread overview] Message-ID: <bug-110304-4-XxAg7A9AlT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110304-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110304 --- Comment #16 from cqwrteur <unlvsur at live dot com> --- ok Would you mind looking at the following link, https://godbolt.org/z/z7K79YMWr, and sharing your thoughts? I would greatly appreciate your feedback. Thank you very much.
next prev parent reply other threads:[~2023-06-20 19:48 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 6:01 [Bug c++/110304] New: __builtin_adcs missing and " unlvsur at live dot com 2023-06-19 6:06 ` [Bug c++/110304] __builtin_adcs missing and jakub " unlvsur at live dot com 2023-06-19 6:12 ` unlvsur at live dot com 2023-06-19 6:16 ` unlvsur at live dot com 2023-06-19 6:19 ` jakub at gcc dot gnu.org 2023-06-19 6:22 ` jakub at gcc dot gnu.org 2023-06-19 6:27 ` unlvsur at live dot com 2023-06-19 6:32 ` unlvsur at live dot com 2023-06-19 6:34 ` jakub at gcc dot gnu.org 2023-06-19 6:37 ` unlvsur at live dot com 2023-06-19 6:54 ` unlvsur at live dot com 2023-06-20 3:08 ` unlvsur at live dot com 2023-06-20 6:45 ` jakub at gcc dot gnu.org 2023-06-20 19:17 ` unlvsur at live dot com 2023-06-20 19:40 ` unlvsur at live dot com 2023-06-20 19:41 ` jakub at gcc dot gnu.org 2023-06-20 19:48 ` unlvsur at live dot com [this message] 2023-06-20 19:50 ` jakub at gcc dot gnu.org 2023-06-20 20:57 ` unlvsur at live dot com 2023-06-20 21:03 ` unlvsur at live dot com
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-110304-4-XxAg7A9AlT@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).