This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

tweaking cse


Is there any way to tell cse how many times a value gets reused before
putting a copy in a register is profitable?  The logic seems to
compare the address costs, but doesn't account for the cost of storing
in the register.  What I'd like is some way of saying the cutoff is N
uses, not the current 2.  For example, if hard coding an address costs
an extra byte, and storing in a register costs four bytes, the cutoff
should be four uses.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]