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 tree-optimization/108341] argument to `__builtin_ctz` should be assumed non-zero when CTZ_DEFINED_VALUE_AT_ZERO says it is undefined Date: Mon, 09 Jan 2023 16:37:51 +0000 [thread overview] Message-ID: <bug-108341-4-GDuJXRZGFN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108341-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108341 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think 0 argument for __builtin_c[lt]z{,l,ll,imax} is always undefined, 0 argument to .C[LT]Z (internal calls) is undefined if C[LT]Z_DEFINED_VALUE_AT_ZERO is not 2 and 0 argument to C[LT]Z RTL is undefined if C[LT]Z_DEFINED_VALUE_AT_ZERO is not non-zero.
next prev parent reply other threads:[~2023-01-09 16:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-09 12:10 [Bug tree-optimization/108341] New: argument to `__builtin_ctz` should be assumed non-zero lh_mouse at 126 dot com 2023-01-09 12:28 ` [Bug tree-optimization/108341] " marxin at gcc dot gnu.org 2023-01-09 15:55 ` aldyh at gcc dot gnu.org 2023-01-09 16:22 ` pinskia at gcc dot gnu.org 2023-01-09 16:37 ` jakub at gcc dot gnu.org [this message] 2023-01-09 18:49 ` [Bug tree-optimization/108341] argument to `__builtin_ctz` should be assumed non-zero when CTZ_DEFINED_VALUE_AT_ZERO says it is undefined amacleod at redhat dot com 2023-01-09 19:02 ` aldyh at gcc dot gnu.org 2023-01-10 8:05 ` lh_mouse at 126 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-108341-4-GDuJXRZGFN@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).