You probably haven't had an answer because there's just been a whole
email thread about this.
Can be found in the archives of the boinc_dev email list, starting
from http://lists.ssl.berkeley.edu/pipermail/boinc_dev/2013-July/020215.html

On Sun, Aug 25, 2013 at 11:49 AM, Radim Vančo <[email protected]> wrote:
> No one to reply this? This is quite important, I already wrote with some
> people and they also have undetected AVX on this type of processor which has
> AVX. So there is some problem in BOINC client, that it doesn't report AVX.
>
> Radim
>
>
> Dne 23.8.2013 11:51, Radim Vančo napsal(a):
>
>> I am now testing 7.0.64 and it also doesn't detect AVX. So it propably
>> something in source code, that it doesn't detect on that processor.
>>
>>
>> Dne 23.8.2013 11:41, Radim Vančo napsal(a):
>>>
>>> Does BOINC client version 7.2.10/7.2.11 detect AVX? I just realized that
>>> mine doesn't, but it should report. Processor i5 3230i and Win 7 64bit with
>>> SP1 installed. Isn't there a bug in BOINC, that it doesn't detect it?
>>> _______________________________________________
>>> boinc_dev mailing list
>>> [email protected]
>>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>>> To unsubscribe, visit the above URL and
>>> (near bottom of page) enter your email address.
>>
>>
>> _______________________________________________
>> boinc_dev mailing list
>> [email protected]
>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>
>
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.



-- 
-- Jord van der Elst.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to