public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109279] RISC-V: complex constants synthesized should be improved Date: Sat, 25 Mar 2023 00:56:57 +0000 [thread overview] Message-ID: <bug-109279-4-tYUnoMwZts@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109279-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109279 --- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is something to look into: #define const1 0x0101010101010101ULL #define const2 0x0080402010080400ULL #define const0 const1 unsigned long long g(unsigned long long occ, const unsigned int sq) { return const0 ; } unsigned long long f(unsigned long long occ, const unsigned int sq) { unsigned long long t= (const0)>>32<<32 ; unsigned long long t1= (unsigned int)(const0) ; asm("":"+r"(t)); return t | t1; }
next prev parent reply other threads:[~2023-03-25 0:56 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 22:04 [Bug target/109279] New: [13 Regression] RISC-V: complex constants synthesized vs. fetching from constant pool vineet.gupta at linux dot dev 2023-03-24 22:08 ` [Bug target/109279] " pinskia at gcc dot gnu.org 2023-03-24 22:08 ` pinskia at gcc dot gnu.org 2023-03-24 22:13 ` vineet.gupta at linux dot dev 2023-03-24 22:15 ` vineet.gupta at linux dot dev 2023-03-24 22:17 ` pinskia at gcc dot gnu.org 2023-03-24 22:29 ` [Bug target/109279] RISC-V: complex constants synthesized should be improved pinskia at gcc dot gnu.org 2023-03-24 22:33 ` pinskia at gcc dot gnu.org 2023-03-24 22:34 ` pinskia at gcc dot gnu.org 2023-03-24 23:33 ` pinskia at gcc dot gnu.org 2023-03-25 0:44 ` vineet.gupta at linux dot dev 2023-03-25 0:48 ` vineet.gupta at linux dot dev 2023-03-25 0:56 ` pinskia at gcc dot gnu.org [this message] 2023-03-25 1:12 ` vineet.gupta at linux dot dev 2023-03-30 18:40 ` vineet.gupta at linux dot dev 2023-05-19 17:31 ` vineetg at gcc dot gnu.org 2023-05-19 18:13 ` vineetg at gcc dot gnu.org 2023-08-15 17:37 ` vineetg at gcc dot gnu.org 2023-10-06 19:37 ` vineetg at gcc dot gnu.org 2023-10-06 19:38 ` vineetg 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-109279-4-tYUnoMwZts@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).