-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/18/11 15:20, dpadgett_mail-...@yahoo.com wrote: > Hello, > > Does gcc IRA provide a mechanism to support spilling to registers > instead of the stack? For the particular target I'm looking at, > there are some non-general-purpose registers that can be copied to > and from more quickly than the stack, so would be preferable to use > as a form of shareable spill slot in some cases. One limitation, > which is perhaps a significant one, is that these registers are not > callee save, so one would only want to save to and restore from them > when there is no intervening function call. If there is no current > support for such a mechanism, any opinions on the value and > practicality of adding one would be much appreciated. Not directly. However, I think this should fall out fairly naturally from the range splitting work I've done.
Dealing with the caller-save issue would be an extension to the existing work, but one well worth doing. The current model of caller-save.c is just a PITA to work with. I believe caller-saving can be modeled as a special case of range splitting. Vlad's LRA work might help as well. jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOJKo2AAoJEBRtltQi2kC7N5IH/2NtJx5wY+xqyX5WbK5zyN4+ sxVP2zmsEvOQxvmGzAJw0KP4fOFI9lmb0R4LLaI+m3oaTeqInRfRDfcQ5iR5zrck tmFc9dV4tXqbNl7XmaGDF5Y7PfXNtiO7++jNGMxVhEIN1N57dPGRm0BjQgDR6X9k zKYDDa11OFqqMxlQAiEfb6V9DVFpj/PCK9dpSlgR3Y4HX/YTwu1YJrjGfaXcqfXW TegFeSTtPdi/YLOtu5cp4+GSA2YE/16mJhX46vWrp2a7Pdd1hG3SLOXIPfcVQzvE WSPlhH+/X4wqT+h+CSCVSFErM3mlayypkpzrVIHlnaSsnqGcCU+EIgqwMEY8bZE= =XqC7 -----END PGP SIGNATURE-----
