public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/19464] [3.3/3.4/4.0 Regression] gcse causes poor register allocation Date: Fri, 21 Jan 2005 12:51:00 -0000 [thread overview] Message-ID: <20050121125115.10504.qmail@sourceware.org> (raw) In-Reply-To: <20050115205816.19464.belyshev@depni.sinp.msu.ru> ------- Additional Comments From steven at gcc dot gnu dot org 2005-01-21 12:51 ------- With my patch I get almost perfect code for amd64: .globl f .type f, @function f: .LFB2: decl %edi je .L6 movl r5(%rip), %r9d movl r4(%rip), %r8d xorl %r10d, %r10d movl r3(%rip), %esi movl r2(%rip), %ecx movl r0(%rip), %edx movl r1(%rip), %eax .p2align 4,,7 .L4: addl %edx, %eax incl %r10d addl %eax, %ecx addl %ecx, %esi addl %esi, %r8d addl %r8d, %r9d addl %r9d, %edx cmpl %r10d, %edi jne .L4 movl %r9d, r5(%rip) movl %r8d, r4(%rip) movl %esi, r3(%rip) movl %ecx, r2(%rip) movl %edx, r0(%rip) movl %eax, r1(%rip) .L6: rep ; ret -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19464
next prev parent reply other threads:[~2005-01-21 12:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-15 20:58 [Bug rtl-optimization/19464] New: " belyshev at depni dot sinp dot msu dot ru 2005-01-15 20:59 ` [Bug rtl-optimization/19464] " belyshev at depni dot sinp dot msu dot ru 2005-01-15 21:04 ` pinskia at gcc dot gnu dot org 2005-01-15 21:44 ` dberlin at dberlin dot org 2005-01-15 21:48 ` dberlin at dberlin dot org 2005-01-21 12:25 ` steven at gcc dot gnu dot org 2005-01-21 12:51 ` steven at gcc dot gnu dot org [this message] 2005-01-23 0:42 ` belyshev at depni dot sinp dot msu dot ru 2005-01-23 1:17 ` pinskia at gcc dot gnu dot org 2005-01-23 1:43 ` belyshev at depni dot sinp dot msu dot ru 2005-01-23 19:36 ` cvs-commit at gcc dot gnu dot org 2005-01-23 19:43 ` steven at gcc dot gnu dot 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=20050121125115.10504.qmail@sourceware.org \ --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).