On 09/01/15 14:55, Martin Lucina wrote: > [email protected] said: >> Based on Martin's observations of differences in the compiled code, I >> observed that you get the unwanted assembly from the stack protector, >> sprinkled -fno-stack-protector into places, and things now work for me >> on an Ubuntu host. > > Great, thanks for fixing this. I presume the reason we got the failure on > Ubuntu but not Debian jessie is that the former enables -fstack-protector > by default?
Yes. NetBSD Makefiles set -fstack-protector by default, but we disable that with USE_SSP=no in buildrump.sh. Didn't realize some compilers have started setting it by default. (note: eventually we should support -fstack-protector, but as this episode shows, it requires a bit of frobbing) > I've added the same flag to the xen/arch/x86/arch.mk just to be consistent. oic, it doesn't use the CFLAGS from xen/Makefile. Good catch, though sharing the CFLAGS would be a better catch. I already had to boot like 4 times during testing making inches of progress with each iteration, because the damn flag had to be added to so many places ;) ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
