public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40718] Invalid code produced with -foptimize-sibling-calls
Date: Sat, 29 Aug 2009 10:26:00 -0000 [thread overview]
Message-ID: <20090829102615.9105.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40718-16926@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from slyfox at inbox dot ru 2009-08-29 10:26 -------
(In reply to comment #15)
> Fixed everywhere.
>
Just tested on my sample (got this only revision from 4_4 branch and applied to
gentoo gcc sources).
All works as expected.
Thanks!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40718
prev parent reply other threads:[~2009-08-29 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 0:06 [Bug middle-end/40718] New: " d dot g dot gorbachev at gmail dot com
2009-08-22 12:09 ` [Bug middle-end/40718] " slyfox at inbox dot ru
2009-08-22 13:38 ` [Bug target/40718] " ubizjak at gmail dot com
2009-08-22 13:43 ` ubizjak at gmail dot com
2009-08-22 13:51 ` ubizjak at gmail dot com
2009-08-22 18:38 ` slyfox at inbox dot ru
2009-08-23 9:09 ` ubizjak at gmail dot com
2009-08-23 9:46 ` uros at gcc dot gnu dot org
2009-08-23 11:12 ` slyfox at inbox dot ru
2009-08-23 11:41 ` ubizjak at gmail dot com
2009-08-23 11:58 ` ubizjak at gmail dot com
2009-08-23 12:08 ` ubizjak at gmail dot com
2009-08-23 12:14 ` uros at gcc dot gnu dot org
2009-08-23 12:38 ` uros at gcc dot gnu dot org
2009-08-23 13:04 ` ubizjak at gmail dot com
2009-08-23 13:04 ` uros at gcc dot gnu dot org
2009-08-29 10:26 ` slyfox at inbox dot ru [this message]
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=20090829102615.9105.qmail@sourceware.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).