public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14909] tail call optimization does not work with indirect call
Date: Sat, 10 Apr 2004 18:16:00 -0000 [thread overview]
Message-ID: <20040410161933.29252.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040410161002.14909.cesarb@nitnet.com.br>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-10 16:19 -------
This is already fixed in 3.4.0:
g:
movl 4(%esp), %ecx
jmp *%ecx
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
Target Milestone|--- |3.4.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14909
next prev parent reply other threads:[~2004-04-10 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 18:16 [Bug optimization/14909] New: " cesarb at nitnet dot com dot br
2004-04-10 18:16 ` pinskia at gcc dot gnu dot org [this message]
2004-04-10 18:21 ` [Bug optimization/14909] " 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=20040410161933.29252.qmail@sources.redhat.com \
--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).