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 tree-optimization/110067] [14 Regression] Wrong code on pixman-0.42.2 Date: Thu, 01 Jun 2023 01:55:26 +0000 [thread overview] Message-ID: <bug-110067-4-C9gdUdc2XL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110067-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110067 --- Comment #4 from Hongtao.liu <crazylht at gmail dot com> --- For br64 = br; br64 = ((br64 << 16) & 0x000000ff00000000ull) | (br64 & 0x0000ff00ull); n->n is 0x3000000200. n->range is 32. n->type is uint64. Currently the code assumes n->range is same as TYPE PRECISION(n->type), and tries to rotate the mask with below code and get new mask as 0x20300 which is incorrect. tmp_n = tmp_n >> count | tmp_n << (range - count) --- Comment #5 from Hongtao.liu <crazylht at gmail dot com> --- For br64 = br; br64 = ((br64 << 16) & 0x000000ff00000000ull) | (br64 & 0x0000ff00ull); n->n is 0x3000000200. n->range is 32. n->type is uint64. Currently the code assumes n->range is same as TYPE PRECISION(n->type), and tries to rotate the mask with below code and get new mask as 0x20300 which is incorrect. tmp_n = tmp_n >> count | tmp_n << (range - count)
next prev parent reply other threads:[~2023-06-01 1:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 22:42 [Bug tree-optimization/110067] New: " slyfox at gcc dot gnu.org 2023-05-31 22:46 ` [Bug tree-optimization/110067] " pinskia at gcc dot gnu.org 2023-05-31 23:28 ` slyfox at gcc dot gnu.org 2023-06-01 1:42 ` crazylht at gmail dot com 2023-06-01 1:55 ` crazylht at gmail dot com [this message] 2023-06-01 1:55 ` crazylht at gmail dot com 2023-06-01 9:46 ` slyfox at gcc dot gnu.org 2023-06-02 7:38 ` rguenth at gcc dot gnu.org 2023-06-02 7:55 ` crazylht at gmail dot com 2023-06-03 0:09 ` cvs-commit at gcc dot gnu.org 2023-06-03 0:10 ` crazylht at gmail dot com 2023-06-03 7:33 ` slyfox at gcc dot gnu.org 2023-06-04 5:08 ` sjames at gcc dot gnu.org 2023-06-05 1:01 ` crazylht at gmail 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-110067-4-C9gdUdc2XL@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).