We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1509

Summary: Improve performance using x86 inline assembly also on x86_64 targets
Product: SDL Reporter: Patrice Mandin <patmandin>
Component: *don't know*Assignee: Ryan C. Gordon <icculus>
Status: RESOLVED ENDOFLIFE QA Contact: Sam Lantinga <slouken>
Severity: enhancement    
Priority: P2    
Version: 1.2.15   
Hardware: x86_64   
OS: All   
Attachments: Patch to use x86 inline asm stuff also on x86_64

Description Patrice Mandin 2012-05-30 09:56:51 UTC 
Created attachment 863 [details]
Patch to use x86 inline asm stuff also on x86_64

Hello,

While investigating some performance difference between 32 and 64 bits build of Aranym emulator, someone found that on 64 bits build, inline x86 asm was not used, and so it was slower in this case.

Philipp Donzé <philippdonze@gmx.ch> wrote the following patch, to enable using x86 asm also on all x86_64 targets.
Comment 1 Ryan C. Gordon 2015-08-25 09:38:20 UTC 
Hello, and sorry if you're getting several copies of this message by email, since we are closing many bugs at once here.

We have decided to mark all SDL 1.2-related bugs as RESOLVED ENDOFLIFE, as we don't intend to work on SDL 1.2 any further, but didn't want to mark a large quantity of bugs as RESOLVED WONTFIX, to clearly show what was left unattended to and make it easily searchable.

Our current focus is on SDL 2.0.

If you are still having problems with an ENDOFLIFE bug, your absolute best option is to move your program to SDL2, as it will likely fix the problem by default, and give you access to modern platforms and tons of super-cool new features.

Failing that, we _will_ accept small patches to fix these issues, and put them in revision control, although we do not intend to do any further official 1.2 releases.

Failing that, please feel free to contact me directly by email (icculus@icculus.org) and we'll try to find some way to help you out of your situation.

Thank you,
--ryan.