public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21596] New: [4.0/4.1 Regression] extra temporaries when using global register variables
Date: Sun, 15 May 2005 23:45:00 -0000	[thread overview]
Message-ID: <20050515234452.21596.rth@gcc.gnu.org> (raw)

register int *reg __asm__("%edi");
int test () { return *--reg <= 0; }

With -O2 -fomit-frame-pointer, 4.0,

        movl    %edi, %eax
        leal    -4(%edi), %edi
        movl    -4(%eax), %eax
        testl   %eax, %eax

With 3.4,

        subl    $4, %edi
        cmpl    $0, (%edi)

The problem appears to begin at the tree level, with extra temporaries:

  reg.0 = reg;
  reg.2 = reg.0 - 4B;
  reg = reg.2;
  return *reg.2 <= 0;

We do consider hard register variables not is_gimple_reg, due to needing
to V_MAY_DEF them at call sites.  It would be nice if we could eliminate
these temporaries during TER, or something.

-- 
           Summary: [4.0/4.1 Regression] extra temporaries when using global
                    register variables
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rth at gcc dot gnu dot org
                CC: amacleod at redhat dot com,gcc-bugs at gcc dot gnu dot
                    org


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


             reply	other threads:[~2005-05-15 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 23:45 rth at gcc dot gnu dot org [this message]
2005-05-15 23:57 ` [Bug tree-optimization/21596] " pinskia at gcc dot gnu dot org
2005-07-08  1:42 ` mmitchel at gcc dot gnu dot org
2005-09-27 16:23 ` mmitchel 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=20050515234452.21596.rth@gcc.gnu.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: 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).