Emulator Issues #157
closedCC flags ignored by Dolphin under GNU/Linux x86_64
0%
Description
What steps will reproduce the problem?
- Download SVN
- Edit SConstruct to add specific CC flags
- Build SVN
What is the expected output? What do you see instead?
OSD info must show SSE3 and dual-core support. Instead, it show 1 core and
sse3 only.
What version of the product are you using? On what operating system?
R290 on GNU/Linux Debian Lenny x86_64.
Please provide any additional information below.
Here the ccflag line i've edited :
ccflags = '-g -Os -fno-strict-aliasing -fPIC -msse2 -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -march=athlon64 -pipe -msse3' + warnings
Updated by gnuraziel about 16 years ago
correction :
It show only one core and SSE2 only, not sse3
Updated by hrydgard about 16 years ago
- Status changed from New to Accepted
It's not ignoring CC flags, it just fails to detect those cpu features. if you know
how to fix it, go hack CPUDetect.cpp.
Updated by gnuraziel about 16 years ago
Well, adding sse3 is easy cause I forced sse3 mode in CPUDetect.cpp and now I see
SSE3 detected by Dolphin by adding sse3 support in the mode64bits loop (crappy, I
know) but detecting core is far more problematic like you said...
Considering you used method provided by AMD as I can see in the code comments and the
fact I'm a total noob at coding this is out of my skills.
I was just reporting a potential issue, that's all ^^
Updated by gnuraziel about 16 years ago
I tried R291 and I've activated Dynarec (no improvement but no more crash/bug) and
Dual-Core and when I launched ZWW I got ton of this :
FIFO out of bounds (sz = 1306298, at 00000000)
FIFO out of bounds (sz = 1306330, at 00000000)
FIFO out of bounds (sz = 1306362, at 00000000)
FIFO out of bounds (sz = 1306394, at 00000000)
FIFO out of bounds (sz = 1306426, at 00000000)
FIFO out of bounds (sz = 1306458, at 00000000)
FIFO out of bounds (sz = 1306490, at 00000000)
FIFO out of bounds (sz = 1306522, at 00000000)
FIFO out of bounds (sz = 1306554, at 00000000)
FIFO out of bounds (sz = 1306586, at 00000000)
FIFO out of bounds (sz = 1306618, at 00000000)
FIFO out of bounds (sz = 1306650, at 00000000)
FIFO out of bounds (sz = 1306682, at 00000000)
FIFO out of bounds (sz = 1306714, at 00000000)
FIFO out of bounds (sz = 1306746, at 00000000)
FIFO out of bounds (sz = 1306778, at 00000000)
FIFO out of bounds (sz = 1306810, at 00000000)
FIFO out of bounds (sz = 1306842, at 00000000)
FIFO out of bounds (sz = 1306874, at 00000000)
FIFO out of bounds (sz = 1306906, at 00000000)
FIFO out of bounds (sz = 1306938, at 00000000)
FIFO out of bounds (sz = 1306970, at 00000000)
FIFO out of bounds (sz = 1307002, at 00000000)
FIFO out of bounds (sz = 1307034, at 00000000)
FIFO out of bounds (sz = 1307066, at 00000000)
FIFO out of bounds (sz = 1307098, at 00000000)
FIFO out of bounds (sz = 1307130, at 00000000)
FIFO out of bounds (sz = 1307162, at 00000000)
FIFO out of bounds (sz = 1307194, at 00000000)
FIFO out of bounds (sz = 1307226, at 00000000)
FIFO out of bounds (sz = 1307258, at 00000000)
FIFO out of bounds (sz = 1307290, at 00000000)
FIFO out of bounds (sz = 1307322, at 00000000)
FIFO out of bounds (sz = 1307354, at 00000000)
FIFO out of bounds (sz = 1307386, at 00000000)
FIFO out of bounds (sz = 1307418, at 00000000)
FIFO out of bounds (sz = 1307450, at 00000000)
FIFO out of bounds (sz = 1307482, at 00000000)
FIFO out of bounds (sz = 1307514, at 00000000)
FIFO out of bounds (sz = 1307546, at 00000000)
I don't know if it's usefull for you, I post it just in case.
Updated by gnuraziel about 16 years ago
May I add that without Dual-Core activated I just have the usual OGL crash reported
as issue 151.
It's probably useless for you but better add it just in case...
Updated by gnuraziel about 16 years ago
Dual-core do not work on AMD system, I have catastrophic perf on Windows Xp x64 with
AMD X2 600+ CPU when I have pretty good perf on Windows Vista x86 with Intel Core2Duo
T7300...
It's like AMD cpu is not fully exploited, seems more like an old K6 with Dolphin.
Updated by nakeee about 16 years ago
This should be working now.
Reopen for newer svn version if you still have problems.