reed kotler
2013-Mar-13 23:50 UTC
[LLVMdev] void TargetLoweringBase::computeRegisterProperties
It seems like this routine is not allocating any memory and could just be called a second time. Does anyone know if that is true? I looked at a bunch of it but did not want to create a memory leak by calling it again if it was doing a "new" indirectly somewhere. I've created a clearRegisterClasses method so that we can start all over. Then I would add register classes again and call computeRegisterProperties. This is so I can switch processor major modes on a function basis. Tia. Reed
Reed Kotler
2013-Mar-14 00:00 UTC
[LLVMdev] void TargetLoweringBase::computeRegisterProperties
On 03/13/2013 04:50 PM, reed kotler wrote:> It seems like this routine is not allocating any memory and could just > be called a second time. > > Does anyone know if that is true? > > I looked at a bunch of it but did not want to create a memory leak by > calling it again if it was doing a "new" indirectly somewhere. > > I've created a clearRegisterClasses method so that we can start all over. > > Then I would add register classes again and call computeRegisterProperties. > > This is so I can switch processor major modes on a function basis. > > Tia. > > ReedI suppose I could just assume it's not allocating memory and run valgrind and see if it's leaking there.
Reasonably Related Threads
- [LLVMdev] changing register classes on a per function basis
- [LLVMdev] initial putback for implementing mips16/nomips16 attributes - please review
- [LLVMdev] proposed change to class BasicTTI
- [LLVMdev] proposed change to class BasicTTI
- [LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working