public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiangning.liu at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52424] dom prematurely pops entries from const_and_copies stack
Date: Wed, 29 Feb 2012 03:54:00 -0000 [thread overview]
Message-ID: <bug-52424-4-u9SFAitSim@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52424-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52424
--- Comment #2 from Jiangning Liu <jiangning.liu at arm dot com> 2012-02-29 03:42:17 UTC ---
> Jiangning Liu reported that the following C code has recently experienced
> degraded performance on trunk. (Jiangning, please fill in the
> Host/Target/Build fields for your configuration, or tell me what they are if
> you don't have access. The problem is not related to specific targets in any
> event.)
>
Seems I don't have access.
Host: arm*-*-*
Target: arm*-*-*
Build: arm*-*-*
next prev parent reply other threads:[~2012-02-29 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:23 [Bug tree-optimization/52424] New: " wschmidt at gcc dot gnu.org
2012-02-29 3:42 ` [Bug tree-optimization/52424] " jiangning.liu at arm dot com
2012-02-29 3:54 ` jiangning.liu at arm dot com [this message]
2012-02-29 9:15 ` rguenth at gcc dot gnu.org
2012-02-29 13:09 ` wschmidt at gcc dot gnu.org
2012-02-29 13:19 ` wschmidt at gcc dot gnu.org
2012-02-29 20:28 ` wschmidt at gcc dot gnu.org
2012-02-29 20:29 ` wschmidt at gcc dot gnu.org
2012-02-29 21:00 ` pinskia at gcc dot gnu.org
2012-02-29 23:18 ` wschmidt 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-52424-4-u9SFAitSim@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: 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).