From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Reduce startup cost of compiler (patch 3)
Date: Tue, 07 Aug 2007 14:30:00 -0000 [thread overview]
Message-ID: <20070807143027.GZ25795@sygehus.dk> (raw)
In-Reply-To: <20070724050556.GD10270@kam.mff.cuni.cz>
On Tue, Jul 24, 2007 at 07:05:56AM +0200, Jan Hubicka wrote:
> * caller-save.c: Include ggc.h, gt-caller-save.h
> (reg_save_code, reg_restore_code): Rename to ...
> (cached_reg_save_code, cached_reg_restore_code): ... those.
> (savepat, restpat, test_reg, test_mem, saveinsn, restinsn): New.
> (reg_save_code, reg_restore_code): New functions.
> (init_caller_save): Do not intialize
> reg_save_code/reg_restore_code tables.
> * Makeifle.in: (gt-caller-save.h): New.
This causes PR target/33011 (frv ICE building libiberty). Somehow.
--
Rask Ingemann Lambertsen
prev parent reply other threads:[~2007-08-07 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 6:51 Jan Hubicka
2007-07-24 12:57 ` Diego Novillo
2007-07-24 15:01 ` Daniel Jacobowitz
2007-07-24 15:09 ` Diego Novillo
2007-08-07 14:30 ` Rask Ingemann Lambertsen [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=20070807143027.GZ25795@sygehus.dk \
--to=rask@sygehus.dk \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
/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).