llvm dev - Aug 2006 - [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction

Thanks, Reid.

I've found that some overrides of allocation_order_begin() calls
MachineFunction getInfo method. this method is not const. However, I think
there could be default const implementation (const_cast of non-const method)
and then allocation_order_begin() could be const.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20060816/4109a977/attachment.html>

On Wed, 16 Aug 2006, Anton Vayvod wrote:
> Thanks, Reid.
> I've found that some overrides of allocation_order_begin() calls
> MachineFunction getInfo method. this method is not const. However, I think
> there could be default const implementation (const_cast of non-const
method)
> and then allocation_order_begin() could be const.
That sounds reasonable to me.  There should probably also be a const 
version of the getInfo method.  If you'd be willing to put together a 
patch, we can get it fixed.

Thanks,

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/

I'm willing :) I don't know how to do it.
What's "to put together a patch"? :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20060816/fb1f0b57/attachment.html>