Thanks, David! That's a good start. I will need to find places in GCC where these parameters are used to monitor the behavior of transformations based on these parameters and be able to change the compiler decisions through ICI to learn how to tune those costs based on program execution time/code size...
Also, I would prefer to concentrate on only most critical/important costs right now (for example, within register allocation, scheduling, etc) since this research is very time consuming ... Cheers, Grigori ======================================== Grigori Fursin, PhD Research Scientist, INRIA, France http://fursin.net/research > -----Original Message----- > From: David Edelsohn [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2008 9:44 PM > To: Grigori Fursin > Cc: 'gcc' > Subject: Re: Help with identifing all cost models in GCC to make it adaptable > ?.. > > Grigori, > > Many of the costs now are handled by GCC parameters. See > gcc/params.def accessed in the source code using PARAM_VALUE. > > Many other cost models use macros with "COST in their name, such as > > TARGET_RTX_COSTS / rtx_cost > BRANCH_COST (and LOGICAL_OP_NON_SHORT_CIRCUIT) > MEMORY_MOVE_COST > REGISTER_MOVE_COST > MAX_CONDITIONAL_EXECUTE > > David
