Date: Tue, 23 Apr 2002 16:06:22 +0200 (CEST) From: Alexander Leidinger <Alexander@Leidinger.net> To: perky@fallin.lv Cc: ports@FreeBSD.ORG Subject: Re: icc-compiled Python Message-ID: <200204231406.g3NE6MtL028702@Magelan.Leidinger.net> In-Reply-To: <20020420015309.A31482@fallin.lv>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Apr, Hye-Shik Chang wrote: >> > (on compiling with icc, I compiled 6 sources with gcc by hand >> > to avoid icc's error hehe.) >> >> Which files and which errors? > > 1. fail on CC=icc ./configure > : just configure with gcc and modify Makefile manually > not clear but it works. ;) Known problem. That's because icc can't link native programs. > 2. some warning messages > : removed -fPIC and -W... options. > (but dynamic linking is working without any problem. ehm.) -kPIC > 3. fails linking on two points (Parser/pgen and libpython2.2.a) > : do with gcc manually What's the error message? > 4. icc error on FreeBSD base headers on some modules > (including Modules/_localemodule.c Modules/socketmodule.c > Modules/_sslmodule.c) > : compile with gcc manually Errors? Which ones? > Everything worked fine except those. > >> Which CPU? > > Intel Pentium III 800MHz. Then I expect a similiar improvement for AMD processors. >> Any chance the files you compiled with gcc instead of icc are related to >> those tests? > > Ah. if Intel allows to distribute icc-compiled binaries. > I didn't read icc license agreement carefully. I think you misunderstood me here. I wanted to know, if some of the slower tests may be a result of some files being compiled with gcc instead of icc. E.g. if you have to compile some string manipulating functions with gcc instead of icc it may be the case that this lead to the slower results for some string operations. Bye, Alexander. -- Failure is not an option. It comes bundled with your Microsoft product. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204231406.g3NE6MtL028702>