2011/5/5 Roman Divacky <rdivacky_at_freebsd.org>: >> Because with clang, -march=native often breaks buildworld, while >> -march=core2 is ok. > > Can you be more specific about this claim? On what CPU are seeing > this breakage? On a Core2 Quad Q9450 and a Core i7 860. I use "core2" on both because that's the most approaching values supported in bsd.cpu.mk and gcc in HEAD. I reverted from "-march=native" to "-march=core2" for two reasons, the first beeing that gcc didn't use the right "-mtune" when using "-march=native" (I think it was using internally "-mtune=generic"). I'll try to be more specific if I can find the tests I was using at that time. The second reason is that with "-march=native", my buildworld often failed with clang, and since I use "-march=core2" I had no issues. I'll try to buildworld with "-march=native" and report back. > Anyway, can you compile and run on that machine this: > > http://lev.vlakno.cz/~rdivacky/Host.cpp Compiled with gcc and clang, both output (on one of the two computers I use most) : roman = corei7 > It's the LLVM CPU autodetection code, it will print the name of > your CPU. I wonder whats the difference to "core2". > > Thank you. roman Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier_at_gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas."Received on Thu May 05 2011 - 12:10:05 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:13 UTC