Also please set +x to html/ops/delete_job_files
did you miss that part or just you don't agree with the change?
many thanks!
Gianfranco
- Messaggio originale -
Da: David Anderson da...@ssl.berkeley.edu
A: Gianfranco Costamagna costamagnagianfra...@yahoo.it
Cc:
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
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
I suggest you re-read the discussion on this subject on this list last month,
starting from
http://lists.ssl.berkeley.edu/pipermail/boinc_dev/2013-July/020215.html
From: Radim Vančo rad...@centrum.cz
To: boinc_dev@ssl.berkeley.edu
Sent: Sunday, 25 August
I have read it, but this is another problem. The processor has AVX
support and OS also. It is Win 7 with SP1 64bit but it doesn't report
AVX. Even with the latest version, but it doesn't report it on these
type of processors. i7 reports it ok, but i5-3230M and other 3xxx
doesn't report it.
That's because 'the latest version' doesn't support it yet.
It'll be in a 7.2 version, AFTER 7.2.11, as soon as the developers
port it to the 7.2 branch.
If you can't wait, you can build a newer BOINC from Master.
I hope so, because in that mailing part there was problem with not
reporting AVX on os that doesn't support it, but it doesn't report it
even on os that does support it.
Dne 25.8.2013 13:14, Jord van der Elst napsal(a):
That's because 'the latest version' doesn't support it yet.
It'll be in
BOINC can not report parts of the CPU that it isn't programmed to report.
So when for instance in 2014 there will be CPUs available with FMA3
and FMA4, you'll first need a new BOINC capable of detecting those
options before that same BOINC will report them.
Even having code added to the source
I know but because it was another problem it the mailing than I suppose
that they solved this but forgot on these new CPUs. As I said, another
problem so that is why I wrote about it.
Dne 25.8.2013 13:41, Jord van der Elst napsal(a):
BOINC can not report parts of the CPU that it isn't
Rom Walton, from the other thread:
I've held off putting this into 7.2 for now. It turns out that
detecting the CPU instruction set is only half of the problem.
We are in the process of getting an updated toolchain for building on
Windows which will allow us to detect if the OS is properly
10 matches
Mail list logo
