public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110921] Relax _tzcnt_u32 support x86, all x86 arch support for this instrunction
Date: Mon, 07 Aug 2023 12:59:09 +0000	[thread overview]
Message-ID: <bug-110921-4-mIqcGnRWaq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110921-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to 罗勇刚(Yonggang Luo) from comment #10)
> (In reply to Hongtao.liu from comment #9)
> 
> > > Without `-mbmi` option, gcc can not compile and all other three compiler
> > > can compile.
> > 
> > As long as it keeps semantics(respect zero input), I think this is
> > acceptable.
> 
> Yeap, it's acceptable, but consistence with Clang/MSVC/ICL would be better.
> That would makes the cross-platform code easier, besides, GCC also works for
> WIN32, that's needs GCC to be consistence with MSVC

Sorry for confusion, I meant generating codes like

f(int, int):                                 # @f(int, int)
        test    edi, edi
        je      .LBB0_2
        rep       bsf eax, edi
        ret
.LBB0_2:
        mov     eax, 32
        ret

w/o mbmi is acceptable as long as it respect zero input.

      parent reply	other threads:[~2023-08-07 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 14:40 [Bug target/110921] New: " luoyonggang at gmail dot com
2023-08-06 17:32 ` [Bug target/110921] " pinskia at gcc dot gnu.org
2023-08-06 17:32 ` pinskia at gcc dot gnu.org
2023-08-07  1:27 ` crazylht at gmail dot com
2023-08-07  1:44 ` crazylht at gmail dot com
2023-08-07  1:52 ` crazylht at gmail dot com
2023-08-07  2:12 ` luoyonggang at gmail dot com
2023-08-07  2:46 ` crazylht at gmail dot com
2023-08-07 10:39 ` luoyonggang at gmail dot com
2023-08-07 11:50 ` crazylht at gmail dot com
2023-08-07 12:36 ` luoyonggang at gmail dot com
2023-08-07 12:59 ` crazylht at gmail dot com [this message]

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-110921-4-mIqcGnRWaq@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).