public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "levo.delellis at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108140] tzcnt gives different result in debug vs release Date: Fri, 16 Dec 2022 08:45:29 +0000 [thread overview] Message-ID: <bug-108140-4-xurLvZKI4v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108140 --- Comment #3 from Levo DeLellis <levo.delellis at gmail dot com> --- It's late and realized I meant to write rbitll but I can't seem to edit/correct my post Jakub ty I'll do just that. Do you happen to know if clang uses the same sanitizers? I didn't seem to get that on clang but it isn't the latest release.
next prev parent reply other threads:[~2022-12-16 8:45 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 8:18 [Bug c/108140] New: " levo.delellis at gmail dot com 2022-12-16 8:28 ` [Bug c/108140] " jakub at gcc dot gnu.org 2022-12-16 8:29 ` jakub at gcc dot gnu.org 2022-12-16 8:45 ` levo.delellis at gmail dot com [this message] 2022-12-16 9:35 ` [Bug middle-end/108140] ICE expanding __rbit amonakov at gcc dot gnu.org 2022-12-16 11:55 ` ktkachov at gcc dot gnu.org 2022-12-19 11:19 ` [Bug target/108140] " cvs-commit at gcc dot gnu.org 2023-01-10 10:26 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-05-09 9:04 ` ktkachov 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-108140-4-xurLvZKI4v@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).