This is the mail archive of the gcc-patches@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]

Re: [IA64] Hookize MEMORY_MOVE_COST



Hi.


From: "Richard Henderson" <rth@redhat.com>
To: "Anatoly Sokolov" <aesok@post.ru>
Sent: Tuesday, June 29, 2010 7:22 PM

On 06/29/2010 12:00 AM, Anatoly Sokolov wrote:
What bit of reload.h is being used here?


The memory_move_cost function declared in reload.h.

... which is not called by ia64_memory_move_cost, so I ask again.


I wish split the back end interface from middle end interface. If the back end
interface is once again will be changed, for example be implemented as
C++ class and TARGET_MEMORY_MOVE_COST target hooks changed to virtual function,
only memory_move_cost function should be changed, all code which uses it will
stay unchanged.


Anatoly.


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