| Re: [AD] CPU capabilities patch |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
>Were I a Jesuit (French expression), I would say that these cpu_* variables
>were semantically read-only anyway, so we had a right to throw them away
>and replace them by cpu_capabilities and macros. Nevertheless, you're
>obviously right...
>
>> #define cpu_mmx (cpu_capabilities & CPU_MMX)
>
IRRC it is legal to set cpu_mmx to zero in order to disable the use of mmx ,
I think it is the only way you can disable mmx. Ofcourse you can still do that
with cpu_capabilities , but cpu_mmx is not strictly read only.
--
Martijn Versteegh