Is common lisp available for 64 bit PowerPC? I have tried to install Steel Bank Common Lisp (SBCL) on my 64 bit PowerPC system which is running Running hat linux, but since SBCL only supports 32 bit PowerPC, I need 32 bit libraries, which are problematic to get on Red Hat Linux, as it has minimal support for 32 bit on 64 bit Power PC. So, my question is, is there any common lisp available that can run directly on 64 bit Power PC?
http://ccl.clozure.com
Clozure CL is available for the following platforms:
Mac OS X 10.6 and later (x86, x86-64)
Linux (x86, x86-64, ppc32, ppc64, armv7l/armv6)
FreeBSD (x86, x86-64)
Solaris (x86, x86-64)
Microsoft Windows XP and later (x86, x86-64)
Related
I had tried to reserve memory on ubuntu OS version 20.04.01 with below kernel grub cmd:
"memmap=1M\$0x100000000" (3 backslashes before $)
but it works and can see memory is reserved,
but when I used another linux machine which uses ubuntu OS version 22.04.01, then memory is not getting reserved.
Believe this should not be OS specific issue, but not sure what can affect this standard behavior. Any hint would be appreciated.
So I have created AppImage file, and I'm testing this file with different flavours of linux distro's, Have checked on 64 bit OS(Ubuntu, CentOS, RHEL) and it works fine, but when I'm running on (Ubuntu-16.04 (32 bit) and CentOS-7.9 (32 bit)), It is not getting opened(have compiled with 32 bits libs only), some issues related to X11 server/Qt libraries,
I have traced down to specific line where it failing and it is call to xcb_send_request_with_fds64() API, I'm attaching backtrace of error, any advice/suggestion would be of great help..
I'm reading this document about how to compile C/C++ code using the Intel C++ compiler and AVX512 support on a Intel Knights Landing.
However, I'm a little bit confused about this part:
-xMIC-AVX512: use this option to generate AVX-512F, AVX-512CD, AVX-512ER and AVX-512FP.
-xCORE-AVX512: use this option to generate AVX-512F, AVX-512CD, AVX-512BW, AVX-512DQ and AVX-512VL.
For example, to generate Intel AVX-512 instructions for the Intel Xeon
Phi processor x200, you should use the option –xMIC-AVX512. For
example, on a Linux system
$ icc –xMIC-AVX512 application.c This compiler option is useful when
you want to build a huge binary for the Intel Xeon Phi processor x200.
Instead of building it on the coprocessor where it will take more
time, build it on an Intel Xeon processor-based machine
My Xeon Phi KNL doesn't have a coprocessor (No need to ssh micX or to compile with the -mmic flag). However, I don't understand if it's better to use the -xMIC or -xCORE?
In second place about -ax instead of -x:
This compiler option is useful when you try to build a binary that can run on multiple platforms.
So -ax is used for cross-platform support, but is there any performance difference comapred to -x?
For the first question, please use –xMIC-AVX512 if you want to compile for the Intel Xeon Phi processor x200 (aka KNL processor). Note that the phrase in the paper that you mentioned was mistyped, it should read "This compiler option is useful when you want to build a huge binary for the Intel Xeon Phi processor x200. Instead of building it on the Intel Xeon Phi processor x200 where it will take more time, build it on an Intel Xeon processor-based machine."
For the second question, there should not be a performance difference if you run the binaries on an Intel Xeon Phi processor x200. However, the size of the binary complied with -ax should be bigger than the one compiled with -x option.
Another option from the link you provide is to build with -xCOMMON-AVX512. This is a tempting option because in my case it has all the instructions that I need and I can use the same option for both a KNL and a Sklake-AVX512 system. Since I don't build on a KNL system I cannot use -xHost (or -march=native with GCC).
However, -xCOMMON-AVX512 should NOT be used with KNL. The reason is that it generates the vzeroupper instruction (https://godbolt.org/z/PgFX55) which is not only not necessary it actually is very slow on a KNL system.
From Agner Fog's micro-architecture manual he writes in the KNL section.
The VZEROALL or VZEROUPPER instructions are not only superfluous here, they are actually
harmful for the performance. A VZEROALL or VZEROUPPER instruction takes 36 clock cycles
in 64 bit mode...
Therefore for a KNL system you should use -xMIC-AVX512for other systems with AVX512 you should use -xCORE-AVX512 (or -xSKYLAKE-AVX512). I use -qopt-zmm-usage=high as well.
I am not aware of a switch for ICC to disable vzeroupper once it is enabled (with GCC you can use -mno-vzeroupper).
Incidentally, by the same logic you should use -march=knl with GCC and not -mavx512f (-mavx512f -mno-vzeroupper may work if you are sure you don't need AVX512ER or AVX512PF).
I'm confused, can NCReport be used in Mac OS X? From the examples given in the Linux files, it seems as if it can support Mac OS X and they even put up license fee for anyone using Mac OS X.
NCReport just answered my email:
Yes, the whole NCReport system is
MacOSX compatible. Engine and Designer
as well. There are several Mac users
of NCReport.
Mac customers compile the project from
source code to themselves. MacOSX
eval package will available soon.
I have already createdrpm file for my application. It works fine for Fedora linux. also the same worked fine for linux mint. But Solaris does not support rpm. So how to create installer package for solaris OS. I have solaris 10 linux as OS.
Thanks
Sunil Kumar Sahoo
The Solaris OS packaging format (pkgadd) is described in this Sun Solaris document.
There is also an open source project called OpenPKG that can be used on most Unix/Linux variants. I have not used it myself though.
Here is an interesting post about converting RPMs to Solaris Pkg.
Solaris packaging is the way to go. It's a little odd when you first look at it, but it's actually not too difficult once you get your head around it.