Carl Witty wrote: > Since > __pyx_base has no components of type (void(*)(void)), an assignment to > a storage location with that type "can't possibly" interfere with an > assignment to __pyx_base (according to the ANSI C aliasing rules), and > gcc is perfectly within its rights to reorder the two.
Blarg. <rant> I'm getting really annoyed by the way the C standards are going. All these tricky rules concerning casting and aliasing are making it very awkward to use the language as a high-level assembler with any confidence that it will do what you ?&^%$ well *tell* it! </rant> -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
