On Thu, 2 Apr 2009, DRC wrote:
If you use MSYS, Cygwin is not necessary. So I think it's safe to say
installing MSYS, MinGW and even NASM on Windows should be as easy or
even more easy than installing MSVC 2008.
Well, except that MSYS doesn't have the AutoTools. So if you insist on
using AutoT
Peter Åstrand wrote:
> The MSVC compiler might be free today, but what about tomorrow? The
> history also indicates that MS moves quite rapidly when it comes to
> development environments: The 2008 version might soon be replaced with
> something new and incompatible. This has happened numerous time
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.
I agree with ge
Peter Åstrand wrote:
> 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 th
On Wed, Apr 01, 2009 at 12:20:37PM -0500, DRC wrote:
> > As for OML, I take it you want to replace the existing SSE2 code as
> > well?
> >
> We wouldn't necessarily have to. We could use OML only for 64-bit, for now.
It doesn't look fine for me to use different approaches for 32bit and
64bit p
On Wed, 01 Apr 2009 15:00:54 -0500
DRC wrote:
> Pierre Ossman wrote:
> > Odd. I guess RGB_PIXELSIZE must have been defined to something strange.
> > Have you checked that jsimdcfg.inc looks sane?
> >
> OK, I figured out the problem. For some reason, the code was using
> macros _DWORD and _MMW
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
W
Pierre Ossman wrote:
> Odd. I guess RGB_PIXELSIZE must have been defined to something strange.
> Have you checked that jsimdcfg.inc looks sane?
>
OK, I figured out the problem. For some reason, the code was using
macros _DWORD and _MMWORD (which aren't defined) instead of DWORD and
MMWORD.
--
Pierre Ossman wrote:
> Handling 32-bit and 64-bit in the same .asm might not be realistic.
> Having two versions, one per arch, is fine with me.
>
Well, that's not really the crux of the problem. The crux of the
problem is getting the function call stuff right for the 64-bit
version. What I'm
On Wed, 01 Apr 2009 03:35:55 -0500
DRC wrote:
> I've been looking into porting libjpeg/SIMD to 64-bit, and thus far,
> it's making my brain hurt. Converting the register names is easy enough
> and can be done through macros, but then the problem becomes how to
> handle the different calling conv
10 matches
Mail list logo
