public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/67413] New: Complex NOP expanded to several operations Date: Mon, 31 Aug 2015 14:43:00 -0000 [thread overview] Message-ID: <bug-67413-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67413 Bug ID: 67413 Summary: Complex NOP expanded to several operations Product: gcc Version: 6.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: glisse at gcc dot gnu.org Target Milestone: --- _Complex unsigned f(_Complex int i){return i;} yields movl %edi, %eax shrq $32, %rdi salq $32, %rdi orq %rdi, %rax ret I read somewhere that complex integers are a deprecated gcc extension, but gcc only warns in pedantic mode, and it should not be too hard to improve the generated code. Note that tree optimizers currently also fail to optimize the corresponding code: long f(long x){ long y = x >> 32; y <<= 32; int z = x; return z | y; } (using & CST instead of >> and << does not help)
next reply other threads:[~2015-08-31 14:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-31 14:43 glisse at gcc dot gnu.org [this message] 2015-09-01 8:36 ` [Bug rtl-optimization/67413] " rguenth at gcc dot gnu.org 2021-12-15 22:08 ` [Bug tree-optimization/67413] " pinskia at gcc dot gnu.org 2021-12-15 22:12 ` pinskia at gcc dot gnu.org 2021-12-15 22:14 ` pinskia 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-67413-4@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).