public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guillaume dot melquiond at ens-lyon dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29042]  New: Useless floating-point stores and loads on x86
Date: Tue, 12 Sep 2006 20:28:00 -0000	[thread overview]
Message-ID: <bug-29042-7904@http.gcc.gnu.org/bugzilla/> (raw)

This is the same testcase as PR26778. This bug is marked as resolved, and the
patch indeed prevents GCC from using useless mmx registers. Concerning integer
operations, the generated assembly got even better than GCC 3.4, as the values
are directly incremented in memory instead of being loaded and stored; no
callee-save register is used anymore. Unfortunately, there is still a
regression with respect to the floating-point stack.

Testcase compiled with -march=pentium3 -O3:

typedef union {
  long long l;
  double d;
} db_number;

double test(double x[3]) {
  double th = x[1] + x[2];
  if (x[2] != th - x[1]) {
    db_number thdb;
    thdb.d = th;
    thdb.l++;
    th = thdb.d;
  }
  return x[0] + th;
}

It may be clearer with a unified diff between the assembly code generated by
3.4.6 and the one by 4.2.0 (svn 2006-09-12). Note: the assembly code for 3.4
was edited by hand in order to reduce the noise due to mismatching integer
registers.

        pushl   %ebp
        movl    %esp, %ebp
        subl    $16, %esp
        movl    8(%ebp), %eax
        fldl    8(%eax)
        fldl    16(%eax)
        fld     %st(1)
        fadd    %st(1), %st
+       fstl    -8(%ebp)
        fsub    %st, %st(2)
        fxch    %st(1)
        fucomip %st(2), %st
        fstp    %st(1)
        jp      .L7
-       je      .L2
+       je      .L9
 .L7:
        fstpl   -16(%ebp)
        addl    $1, -16(%ebp)
        adcl    $0, -12(%ebp)
        fldl    -16(%ebp)
+       fstpl   -8(%ebp)
+       jmp     .L2
+       .p2align 4,,7
+.L9:
+       fstp    %st(0)
+       .p2align 4,,15
 .L2:
+       fldl    -8(%ebp)
        faddl   (%eax)
        leave
        ret

The 3.4 code never stores the value of th; it is kept at the top of the
floating-point stack. In my opinion, this is optimal. This is no longer the
case with 4.2 code. The value of "th" is stored in -8(%ebp). Then, on one
branch (L7), it is overwritten with the content of -16(%ebp). And on the other
branch (L9), the value is discarded from the top of the stack and then
immediatly (L2) reloaded from memory. Each line prefixed by + is useless: if
none is present, the code will still behave correctly and it will contain five
assembly instructions less.


-- 
           Summary: Useless floating-point stores and loads on x86
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: guillaume dot melquiond at ens-lyon dot fr


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29042


             reply	other threads:[~2006-09-12 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 20:28 guillaume dot melquiond at ens-lyon dot fr [this message]
2006-10-30  2:17 ` [Bug target/29042] [4.0/4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
2006-11-01 18:23 ` mmitchel at gcc dot gnu dot org
2007-02-03 20:05 ` gdr at gcc dot gnu dot org
2007-02-03 21:01 ` pinskia at gcc dot gnu dot org
2007-02-14  9:20 ` mmitchel at gcc dot gnu dot org
2007-06-18  5:29 ` [Bug target/29042] [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org
2008-07-04 21:31 ` [Bug target/29042] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 19:37 ` jsm28 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=bug-29042-7904@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: link
Be 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).