How faster for decoding if its optimazation is implemented for AMD64 platform? Although SSE2 of AMD CPU (Trion, Althon64 and Opetron. Not Intel CPU) is slower than Intel CPU (except to Pentium M), since MMX assmebler doesn't work on MSVC for AMD64, I should try it.

cinfo.err = jpeg_std_error(&jerr);
jpeg_create_decompress(&cinfo);
cinfo.dct_method = JDCT_ISLOW;

jpeg_stdio_src(&cinfo, input_file);
jpeg_read_header(&cinfo, TRUE);

jpeg_start_decompress(&cinfo);

width = cinfo.output_width;
height = cinfo.output_height;

img = (JSAMPARRAY)malloc(sizeof(JSAMPROW)*height);

for(i = 0; i < height; ++i)
	img[i] = (JSAMPROW)calloc(sizeof(JSAMPLE), 3 * width);

while (cinfo.output_scanline < cinfo.output_height)
	jpeg_read_scanlines(&cinfo, img + cinfo.output_scanline, cinfo.output_height - cinfo.output_scanline);

jpeg_finish_decompress(&cinfo);
jpeg_destroy_decompress(&cinfo);

Result. It is 15% faster than origianl!

Also, source code is available on http://hg.mozilla-x86-64.com/firefox-win64/. See jpeg directory.

Mike's session is about current mobile web broswer design. You know, current Web broswer is 2 types, redering server typle and redering client type. Opera Mini and Skyfire is the example of former. Opera Mobile, Safari and S60 Browser is others. Mike's presentation is for beginner for bisuness people.

Jay's session is about Firefox mobile. He explain that it is designed how is matched for mobile device.. Also, he said that it will be released at late of 2008.

Also, pictures are here (http://www.flickr.com/photos/41841117@N00/sets/72157603934505259/).

Latest Mozilla build system uses MSYS. But current stable version of MSYS doesn't work on Vista x64. Since latest Mozilla build system package uses stable version, it doesn't work well.

This issue is a famous issue. Because this is compatibility issue of Vista's WOW6432. To fork thread/process on Cygwin/MSYS, it uses CreateProcess() API and STARTUPINFO parameter. Due to a lack of Vista WOW6432 compatibility, it cannot pass fork information to waiting funtion. So sicne The wait object become invalid, fork always failed.

This issue already fix on latest code (version "1.0.11"). But it isn't released as stabled package. So you have to replace MSYS-1.0.DLL into \mozilla-build\msys\bin with 1.0.11 binaries. MSYS team has released 1.0.11 version DLL as MSYS-1.0.11-20071204.tar.bz2. After installing Mozilla build system, you extract it and have to replace DLLs.

There is 2 CPU arch for Win64

• IA64 (aka Itanium)
• x64 (aka AMD64, x86_64)

Win64 tools such as complier and assember are included in the following products.

• Platform SDK for Windows Server 2003
• Visual Studio 2005 Standard Edition or highr edition

Visual Studio 2005 Express Edition doesn't have Win64 complier and linker. If you want to get Win64 build environment by non-fee, you have to use Platfrom SDK for Windows Server 2003. Platform SDK has version 14.x of CL.EXE (as same as major version of Visual Studio 2005).

Also, how about Platform SDK for Windows Vista? It is not good chooise. Becasue, it doesn't include assember such as ML64.EXE. Although I don't know why Microsoft decides it has no assember command, we must buy VS2005 STD/PRO if you need latest compiler and assember.

At first Mike Shaver who is Mozilla Corp's director speaks Mozilla Eco-systems. But, since it is absolute contents and most Japanese is shy, Q&A session is not warmed up.

Next, Basil presentated Mozilla Lab from Mozilla Corp office, and then, Dan talked about now bookmark system "Place". Although I am interesting with Place using SQLite, this session is only summay of Place.

Last session of AM is from Google, Inc and Yahoo JAPAN community. Google's presentation was a lack of contents for Firefox, they explained only Google API for thier business. Then, Yahoo JAPAN community talked about current Yahoo JAPAN API, not Yahoo API. I think that this session is really needed?

Notes: NSIS is 32-bits, so default install path is \Program Files (x86) directory.

http://benjamin.smedbergs.us/blog/2007-03-02/mozilla-build-system-now-requiring-python-and-new-windows-build-package/

As long as I install it, in other word,

Old Mozilla Build System = Cygwin + NSIS + 7ZIP + UPX

New Mozilla Build System = MSYS + NSIS + 7ZIP + UPX + Python

Cygwin replaces with MSYS and add Python script. So I must port NSIS and SCON that is needed to build NSIS.

GAS (GNU Assembler) vs MASM (Microsoft Macro Assembler)

You know, GNU AS uses AT&T format and MASM uses Intel format.

AT&T format

Intel format

About this different, it is easy using script like perl or making converter. By modifing id software's converter, I resolve this.

Call parameter

At first, you have to understand call parameter registers.

ABI x86-64

Windows x86-64

So, you have to consider parameter registers.

Why were these removed from SDK??

So, now, I am thinking about porting CYGWIN (GCC / BINUTILS) to x64. I reseach source code on latest CVS, it doesn't support PE/COFF x86-64 and GCC doesn't support Win64 way of parameter passing.

I am looking for new idea to port it...

NOTE:

• Must select custom setup and un-check "Quality Feedback Agent". If you select it, setup shows error dialog and doesn't finish.
• This is a test binary. So we don't file a bug to bugzilla.

Also, when I built XULRunner, this seems to works fine. Why does this issue occurs on Firefox only??

So I built this for Windows XP x64 (I need modify several parts of source code). If you want this, please try synergy-win64-20060208.zip. Also, patch is here.