|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> The check is done by calling a windows system information function that asks if
> SSE2 is available. So either that call is not being done properly, or Windows
> says it has SSE when it doesn't.
Perhaps the installer could show the user the selections it has made and
allow the user to change them if they are wrong for some reason?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> Chris Cason <del### [at] deletethistoopovrayorg> wrote:
>> The check is done by calling a windows system information function that asks if
>> SSE2 is available. So either that call is not being done properly, or Windows
>> says it has SSE when it doesn't.
>
> Perhaps the installer could show the user the selections it has made and
> allow the user to change them if they are wrong for some reason?
This is a good idea, I'll see if I can add that without making things too
confusing.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Attwood wrote:
> On my system the installer selected SSE2 which is unavailable,
> so the shortcut crashed. How is it doing the query to check?
I discovered a fault in the installer that would cause this. I've updated
it on the website.
thanks for the report,
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I read some time ago that the POV-Team was using a donated Intel VC++
package to compile POV-Ray, is this still true?
Regards.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Forgot to ask: Any AMD CPUs support? If VC++ is used obviously wont be any.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Saul Luizaga wrote:
> Forgot to ask: Any AMD CPUs support? If VC++ is used obviously wont be any.
Intel VC++ I meant
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/27/2009 6:36 AM, Saul Luizaga wrote:
> Saul Luizaga wrote:
>> Forgot to ask: Any AMD CPUs support? If VC++ is used obviously wont be
>> any.
> Intel VC++ I meant
VC++ is Visual C++, which is owned by MS.
The Intel C Compiler is ICC.
The current beta is compiled with MSVC8 (VC2005, I believe).
And Intel and AMD chips actually both support most of the same
instruction sets, so that's really not a problem.
--
...Chambers
www.pacificwebguy.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Saul Luizaga <sau### [at] netscapenet> wrote:
> Forgot to ask: Any AMD CPUs support? If VC++ is used obviously wont be any.
With Intel's 64-bit stuff on non-Itanium processors being a copy of AMD's 64-bit
x86 extensions, there's no need to worry about lack of AMD CPU support.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Saul Luizaga <sau### [at] netscapenet> wrote:
> I read some time ago that the POV-Team was using a donated Intel VC++
> package to compile POV-Ray, is this still true?
There's no such a thing as "Intel VC++". There is a "MS VC++" and there's
an Intel C++ compiler. Are you referring to the latter?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> Saul Luizaga <sau### [at] netscapenet> wrote:
>> I read some time ago that the POV-Team was using a donated Intel VC++
>> package to compile POV-Ray, is this still true?
>
> There's no such a thing as "Intel VC++". There is a "MS VC++" and there's
> an Intel C++ compiler. Are you referring to the latter?
>
I'll answer all here.
Yes I was referring to the latter, my mistake, I read on an very old
post that The POV-Team had licensed for free a C compiler to make the
official releases of POV-Ray AND Intel has said that WILL NOT support
any AMD features since they are competence and that they copy Intel
stuff and not the other way around, of course this is a lot of bull...
but since you say now is MSVC++ then would be great to include
extensions, in the parts where they fit to accelerate IDE and rendering,
because AMD have at some point different extensions than Intel and maybe
more useulf in certain parts of the code, IMO would be a mistake not
to use a compiler that wont take advantage of those extensions.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |