On Thu, Nov 29, 2007 at 02:09:27PM +0530, Ramana Radhakrishnan wrote: > Hi Michael, > > I had a comment / query regarding Stage 2 where you talk about > Function cloning for different targets. > > I understand that the mechanism is to have a hidden function pointer > that actually gets initialized based on the cpuid. > > I don't know if it is worth the effort to have debug info also > enhanced to be such that a breakpoint put on the function my_min > actually sets the breakpoint on any of the clones since the logic > would be similar to the same. This sounds logically similar to the > way that gdb currently handles breakpoints to multiple constructors. > > The other option ofcourse is to fake debug information for such to > actually set a breakpoint on the value of the function pointer that > you so set up. I am no DWARF expert but there might be other folks on > the list who might have better ideas about how to implement this.
I must admit I hadn't thought much about debugging. I guess I was assuming the cloning that we already support in the compiler had solved the debug problem, but that is a whole other discussion that is going on right now. -- Michael Meissner, AMD 90 Central Street, MS 83-29, Boxborough, MA, 01719, USA [EMAIL PROTECTED]
