Hi Cinap, I see what you are saying about wanting /proc/n/fpregs for both debuggers vs note handlers themselves. I think debuggers are more likely, so fpregs should be the current FP registers (if you're in a note handler, it's the handler's registers). I would suggest /proc/n/notefpregs for the fp registers at the time a note arrived, and that the file returns a read error if a note is not being handled.
As for pushing all the register save/restore logic into Go, that still doesn't make any sense to me. Again, C programs benefit from this just as much as Go programs do. I don't see why every Plan 9 C program should have to link in a copy of the same FP saving logic when the kernel can just do it in one place. I only did 386 and amd64, but I think it would make sense (and should not be too hard) to apply the change to all architectures. Programs that do some floating point in a note handler shouldn't only run on a subset of systems. I will leave the other architectures to the people who maintain Plan 9. Best, Russ ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Taf6b900592afc500-M0f06f2e1648bd6a697d9d11a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
