On Wed, 1 Apr 2009, DRC wrote:
I'm a bit sceptical about intrinsics. Those have been riddled with bugs,
primarily with regard to alignment. Do you have any information on
which compilers have implemented these properly?
I've successfully used OML on Linux and Mac and Cygwin with GCC 4 and on
Win32 with MSVC 2008. It's a lot less of a requirement than requiring
NASM v2.00 or later.
Regardless of which libraries we decide to use, we need to select a decent
assembler. In my opinion, NASM is a great assembler. Before we decided to
use it for SIMD/jpeg, we evaluated different options and NASM certainly
looked like the most promising solution, and I think it still does.
MSVC 2008 is certainly a problematic requirement for many people. As we
have discussed before, one idea, which I still believe we should
implement, is to get rid of all MS compiler dependencies. This means that
the Autotools toolchain, GCC, and NASM could be used an all platforms.
It's true that NASM 2.0 isn't yet available on most distros such as RHEL5.
But still, 2.0 was released more than one year ago. It's likely that it
will be included in most future distributions, perhaps RHEL 5.4 and 6.0?
Until then, installing NASM 2.0 seems to be very easy. I just tried it on
our RHEL5 system:
# wget http://www.nasm.us/pub/nasm/releasebuilds/2.05.01/nasm-2.05.01-1.src.rpm
# rpmbuild --rebuild nasm-2.05.01-1.src.rpm
# rpm -vhU /usr/src/redhat/RPMS/i386/nasm-2.05.01-1.i386.rpm
Seems to work great. There are even binaries available for many platforms.
Best regards,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
