On Wednesday 12 March 2008 15:07:08 Andy Lester wrote: > On Mar 12, 2008, at 4:50 PM, Andy Dougherty via RT wrote: > > The problem is twofold: > > I'm not sure what you're saying is a problem. Are you saying that the > use of __attribute__nonnull__ is a problem? Or just that we don't > have it set correctly everywhere?
I believe he means the latter. If GCC uses these hints during optimization and Parrot crashes in places where it tries to dereference NULL pointers (and in fact this is what happens), then the annotations are wrong for the state of the code. Whether this means the annotations need to change or the code, I don't know yet. -- c
