public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cesarb at nitnet dot com dot br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14909] New: tail call optimization does not work with indirect call
Date: Sat, 10 Apr 2004 18:16:00 -0000 [thread overview]
Message-ID: <20040410161002.14909.cesarb@nitnet.com.br> (raw)
(since I have nothing better to do, here's another sibcall bug)
When compiling:
void g(void (*f)(void)) { f(); }
With:
gcc -W -Wall -Os -fomit-frame-pointer -save-temps -c
The result is:
g:
call *4(%esp)
ret
It should be:
g:
jmp *4(%esp)
The same happens when returning something other than void (my original testcase
used unsigned int).
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib
--enable-nls --without-included-gettext --enable-__cxa_atexit
--enable-clocale=gnu --enable-debug --enable-java-gc=boehm
--enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.3 (Debian 20040401)
--
Summary: tail call optimization does not work with indirect call
Product: gcc
Version: 3.3.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: cesarb at nitnet dot com dot br
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14909
next reply other threads:[~2004-04-10 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 18:16 cesarb at nitnet dot com dot br [this message]
2004-04-10 18:16 ` [Bug optimization/14909] " pinskia at gcc dot gnu dot org
2004-04-10 18:21 ` gdr at integrable-solutions dot net
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=20040410161002.14909.cesarb@nitnet.com.br \
--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).