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 tree-optimization/21046] move memory allocation out of a loop
Date: Fri, 15 Apr 2005 13:37:00 -0000 [thread overview]
Message-ID: <20050415133716.12124.qmail@sourceware.org> (raw)
In-Reply-To: <20050415124156.21046.tkoenig@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-15 13:37 -------
(In reply to comment #1)
> I would think this is much more easily done in the frontend itself, which has a
> higher level representation so that it is much easier to hoist and reuse
> allocations.
Not really true anymore.
Confirmed, related to PR 19831.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Keywords| |missed-optimization
Last reconfirmed|0000-00-00 00:00:00 |2005-04-15 13:37:14
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21046
next prev parent reply other threads:[~2005-04-15 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 12:42 [Bug tree-optimization/21046] New: " tkoenig at gcc dot gnu dot org
2005-04-15 13:04 ` [Bug tree-optimization/21046] " giovannibajo at libero dot it
2005-04-15 13:37 ` pinskia at gcc dot gnu dot org [this message]
[not found] <bug-21046-10391@http.gcc.gnu.org/bugzilla/>
2010-04-29 9:33 ` rguenth at gcc dot gnu dot org
[not found] <bug-21046-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 12:49 ` xiaoyuanbo at yeah dot net
2014-12-25 12:16 ` tkoenig at gcc dot gnu.org
2020-11-11 9:22 ` tkoenig 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=20050415133716.12124.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).