public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/15473] New: [tree-ssa] Sibcall optimization for libcalls.
Date: Mon, 17 May 2004 00:47:00 -0000	[thread overview]
Message-ID: <20040516100200.15473.kazu@cs.umass.edu> (raw)

Consider:

long long
foo (long long a, long long b)
{
  return a / b;
}

I get:

foo (a, b)
{
<bb 0>:
  return a_1 / b_2;

}

with the assembly code being

foo:
	subl	$12, %esp
	pushl	28(%esp)
	pushl	28(%esp)
	pushl	28(%esp)
	pushl	28(%esp)
	call	__divdi3
	addl	$28, %esp
	ret

Note that the sequence of 4 pushl instructions simply copy 16 bytes
from one location of the stack to another.

If I create a (non-libcall) function with the same arguments like so

long long div64 (long long a, long long b);

long long
bar (long long a, long long b)
{
  return div64 (a, b);
}

I get:

bar (a, b)
{
  long long int T.0;

<bb 0>:
  T.0_3 = div64 (a_1, b_2) [tail call];
  return T.0_3;

}

with the assembly code being

bar:
	jmp	div64

-- 
           Summary: [tree-ssa] Sibcall optimization for libcalls.
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Keywords: pessimizes-code
          Severity: enhancement
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kazu at cs dot umass dot edu
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-05-16 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17  0:47 kazu at cs dot umass dot edu [this message]
2004-05-17  0:57 ` [Bug tree-optimization/15473] " pinskia at gcc dot gnu dot org
2004-05-17 19:33 ` [Bug rtl-optimization/15473] " steven at gcc dot gnu dot org
2004-08-16  0:19 ` pinskia 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=20040516100200.15473.kazu@cs.umass.edu \
    --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).