Apple Silicon <Added some Pics>

[curt2go]

Not getting anywhere with MicroSoft. :(

[Ttelmah]

Problem is of course, that it is not a floating point error.
It is an execution error somewhere in the compiler leading to distorted values.

[curt2go]

Valid, but how then how do we pose the question to get the best answer do you think?

[temtronic]

Kinda curious...
why do you use a MAC when CCS was developed for a PC ?

[Ttelmah]

On how to ask, you would have to work through the compiler assembler
to find what is being executed, and post this. This CCS might be able to
help with by giving the source code for that small section, and what compiler
they use. I have a feeling I worked it out a while ago, as Delphi.
Jay, we always tend to upgrade to faster and more capable chips.
Historical compatibility, may get sacrificed on the way. The M series chips
are very capable of graphics, but their performance in other areas is less
impressive. Their power consumption is better than the Intel systems,
but unless you are going to throw all your old software, you are dependant
on how good the emulation abilities are. Most issues are with timings and
peripheral support. Must admit I've not found one yet with basic execution
of i386 code. This is the first example I have seen.

[curt2go]

I use a Mac because of XCode and app development. Before i started building Apps, I always used a PC. Apple makes things difficult when using XCode and the Apps store on a PC. It may be better now , but when i started you needed an Apple for all of that. So I have just stuck with it.

[asmallri]

[curt2go]

Still getting no where on this. No response from CCS . I even asked then if they were going to look into it. As i would wait if they could make a work around. But nothing. They are usually really good.

Is it possible that parallels will ever make a fix or it is in the Prism emulator from MS , so they have no way of doing that?

[newguy]

No response (usually) = not our problem.

You're going to have to track down a workaround elsewhere; CCS likely wants nothing to do with it.

[jeremiah]

[Ttelmah]

It's the Prism emulator.
The point is you are running Windows ARM. This is the Windows OS, that
runs on the ARM processors, and contains inside it code to allow Intel
applications to run. Parallels allows this to be run as an OS inside the
Mac OS's, rather than having to be installed instead.
Must admit the more I'm looking t this the more puzzled I am. Prism pretty
much handles every Intel instruction as closely as the different procesors
like AMD do. The problems normally code from things like graphics and
device interfacing, not the core emulation. What is odd, is that my system
refuses to make the errors you are seeing. I've tried dozens of different
numbers and all come out the same both on Intel and ARM.

[curt2go]

Ttelmah , yeh its crazy. In the past i have had a few hiccups here and there and actually this computer had no other issues, which sucks cause i cant move to this computer without getting this fixed.

I appreciate all the help so far on this. I will contact CCS again, i know its not their issue , but they may be able to work around it.

I'm still not to sure where or how to put it as a Prism issue for MS to look at or on the forums.

Ttelmah , what version of M4 do you have? Could this issue still be something i am doing wrong?

Sorry for the stupidity on this, i just woudl liek to solve it.

[Ttelmah]

Yes it could. As I said before, mine is a desktop, not the Macbook.
It's the 10core 24" unit.However, not the Pro, and they say that the Mac
Book, can run the processor harder than the desktop, since it has active
cooling. Is yours the 10core tr the 8 core unit?.

[curt2go]

its 10 CORE model num : MCX04LL/A 24g of mem.

I could try to give the parallels more CPU's ? Or that is just not going to do anything?

Jeremiah you were right. They were not getting my messages. I went on their chat and got my emails flowing to them. Thanks for the idea.

[Ttelmah]

That's good. The real magic thing, would be if someone there has an
M4 machine and can duplicate the fault. I asked early on what number
you actually used to give the results you show in the hex?.
That might allow the behaviour to be found.