public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/47028] [4.6 Regression] gcc.dg/tree-ssa/tailrecursion-[57].c FAIL with -foptimize-sibling-calls -fno-forward-propagate -fno-tree-copy-prop -fno-tree-dominator-opts Date: Mon, 27 Dec 2010 19:06:00 -0000 [thread overview] Message-ID: <bug-47028-4-OmvQPfaxwN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47028-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47028 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org Target Milestone|--- |4.6.0
next prev parent reply other threads:[~2010-12-27 19:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-20 18:56 [Bug rtl-optimization/47028] New: " zsojka at seznam dot cz 2010-12-20 19:20 ` [Bug rtl-optimization/47028] " zsojka at seznam dot cz 2010-12-27 19:06 ` jakub at gcc dot gnu.org [this message] 2010-12-30 13:19 ` jakub at gcc dot gnu.org 2010-12-30 14:44 ` hjl.tools at gmail dot com 2010-12-30 16:00 ` jakub at gcc dot gnu.org 2010-12-30 18:57 ` rguenth at gcc dot gnu.org 2011-01-02 17:07 ` jakub at gcc dot gnu.org 2011-01-02 17:24 ` jakub at gcc dot gnu.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=bug-47028-4-OmvQPfaxwN@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).