From: Joern Rennecke <joern.rennecke@superh.com>
To: qiong.cai@gmail.com
Cc: wilson@specifixinc.com (James E Wilson), gcc@gcc.gnu.org
Subject: Re: number of spills and reloads
Date: Wed, 01 Sep 2004 12:35:00 -0000 [thread overview]
Message-ID: <200409011238.i81Ccef11137@chloe.uk.w2k.superh.com> (raw)
In-Reply-To: <fd80a3de040901005373d62cf3@mail.gmail.com> from "Qiong Cai" at Sep 01, 2004 05:53:24
> I'm doing some experiments on Pentium machines, and basically I need 3 kinds
> of statistics after reloading:
> 1) number of memory stores, eg. [sp+4] <- r1
> 2) number of memory loads, eg. r1 <- [sp+4]
> 3) number of combined stores and loads with addressing mode available
> on CISC-like architectures: eg. [sp+4] <- [sp+4] + r1, or r1 <- [sp+4]
> + r1
> where r1 is the hardware register.
>
> >From your previous email, I think the place in which REG is modifed
> into MEM is only for case 3)?? Could you please tell me which
No, a reg->reg move can have either or both operands changed to a MEM,
thus making it a load, a store, or a memory-memory move (where available).
> functions in the codes does this modification?
Look at alter_reg.
> >From the greg dump, it seems that the memory stores is related to
> RELOAD_FOR_OUTPUT. Is it possible to obtain (1) from the function
> "emit_output_reload_insns"?
>
> For case (2), I don't have much clue. Is it related to RELOAD_FOR_INPUT?
> For the dump, it seems that for any non-optional RELOAD_FOR_INPUT or
> RELOAD_FOR_OPERAND_ADDRESS, a "memory load" will be generated.
> Is it correct?
A memory access need not have been generated by reload changing a register
into a memory reference; it might also be a result of rtl generation.
next prev parent reply other threads:[~2004-09-01 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 16:04 Qiong Cai
2004-08-25 23:43 ` James E Wilson
2004-08-26 9:04 ` Qiong Cai
2004-08-31 0:48 ` James E Wilson
2004-09-01 7:53 ` Qiong Cai
2004-09-01 12:35 ` Joern Rennecke [this message]
2004-09-01 14:02 ` Qiong Cai
2004-09-01 15:32 ` Joern Rennecke
2004-09-01 20:18 ` James E Wilson
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=200409011238.i81Ccef11137@chloe.uk.w2k.superh.com \
--to=joern.rennecke@superh.com \
--cc=gcc@gcc.gnu.org \
--cc=qiong.cai@gmail.com \
--cc=wilson@specifixinc.com \
/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).