Forum > Discussion Forum
opt. SETI@home AP app?
Josef W. Segur:
FWIW, I believe the AP application is built with VS 2005 or VS 2008. Apps built with DevC++/MinGW generally link to msvcrt.dll, I'm not even sure it's possible to go to static linkage for that runtime code. Dependancy Walker doesn't show any direct usage of msvcrt.dll, though of course there's indirect usage through the fftw dll built with MinGW.
AP also does have the linkage to IsDebuggerPresent in Kernel32.dll symptomatic of recent MS compilers lack of Win95 compatibility.
Joe
Jason G:
--- Quote from: Josef W. Segur on 01 Aug 2008, 01:57:17 pm ---FWIW, I believe the AP application is built with VS 2005 or VS 2008. Apps built with DevC++/MinGW generally link to msvcrt.dll, I'm not even sure it's possible to go to static linkage for that runtime code. Dependancy Walker doesn't show any direct usage of msvcrt.dll, though of course there's indirect usage through the fftw dll built with MinGW.
AP also does have the linkage to IsDebuggerPresent in Kernel32.dll symptomatic of recent MS compilers lack of Win95 compatibility.
Joe
--- End quote ---
Ahh ok, not a lot of 'easy' optimisation leverage with that combo then. Might be an opportunity to resolve the win95 issue 'properly' early on and verify that no clr startup stuff has crept in 'accidentally'. I wonder do Linux builds, presuming there are some, demonstrate similar performance characteristics...
Jason
Sutaru Tsureku:
How it's looking? There are some news because of a date of publishing an opt. AP-app? :)
Ahh.. yes.. my QX6700 need SSSE3..
..and my old Athlon 600 need MMX..
;D
Jason G:
LoL, sorry not anytime soon Sutaru. We're just wetting our feet in what is going to be a big, long term project (not just a simple recompile this time). What helps a lot is that the code does look very well organised in key places, with exceptionally helpful comments, and will likely facilitate modifications for good current machines and future hardware as well. Sadly, I can't recommend that MMX will ever be useful or practical for AstroPulse, though SSE and up are being considered.
Cheers, Jason
WHRoeder:
--- Quote from: Sutaru Tsureku on 28 Jul 2008, 01:53:35 pm ---How must look my current app_info.xml that my rigs can download AP WUs?
--- End quote ---
--- Code: ---<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>astropulse_4.35_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_graphics_4.35_windows_intelx86.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>435</version_num>
<file_ref>
<file_name>astropulse_4.35_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_graphics_4.35_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSE2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>527</version_num>
<file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
--- End code ---
reference: Advanced Users
Navigation
[0] Message Index
[*] Previous page
Go to full version