|
From: Chitlesh G. <chi...@wa...> - 2007-05-12 08:51:47
|
On Saturday 12 May 2007 04:52:07 Bill Richards wrote: > Hi, and thanks for the reply.=C2=A0 Could you tell me what compiler flag= s were > actually used for the x86_64 package? As I mentioned in my previous post,= I > made a clean binary from source and found exactly the same results.=C2=A0= I > think the x86_64 package is OK-=C2=A0 I think my system configuration is = not > right somehow... /proc/cpuinfo reports the following: > the Fedora specific compilation flags for 32 bit arch is =2DO2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=3D2 -fexceptions -fstack-protect= or =2D-param=3Dssp-buffer-size=3D4 -m32 -march=3Di386 -mtune=3Dgeneric =2Dfasynchronous-unwind-tables I guess for x86_64 arch it should be=20 =2DO2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=3D2 -fexceptions -fstack-protect= or --param=3Dssp-buffer-size=3D4 -m64 -mtune=3Dgeneric for more details on your arch: $ rpm --showrc | grep flags=20 and pay attention to : * optflags * global_cflags Like I said before, I'm open for any improvement of the ngspice package=20 especially for the x86_64 arch since, I don't have the specific arch to tes= t=20 it, not even at my university. :( regards, Chitlesh |