7 ms·

Do Some apps not run on m1? I’ve never heard this.

by rc_mob 6y ago

refactor_master 6y ago
I have a PyInstaller-compiled Qt .app that crashes on startup. Weird, because Intel Python in Intel PyCharm is actually working just fine.
The_rationalist 6y ago
Docker for example (might have been fixed now)
- bluedino 6y ago
  Docker works you just can’t virtualize x86 images
  - LukeLambert 6y ago
    The tech preview[1] works and you can run x86 images (though you get a warning from the CLI). [1] https://www.docker.com/blog/download-and-try-the-tech-preview-of-docker-desktop-for-m1/ https://www.docker.com/blog/download-and-try-the-tech-previe...
tonyedgecombe 6y ago
I would assume it's because they depend on the JVM.
- millerm 6y ago
  X86 JVM runs fine under Rosetta2. Will will be faster now. Looking forward to it!
epilogue 6y ago
As mentioned in the release notes IntelliJ ran under Rosetta 2 previously (Apples x86 to ARM emulation layer) but this new release adds native ARM (Apple Silicon) support.
millerm 6y ago
I believe they’re just referring to the fact it’s native and it’s no longer being utilizing Rosetta2. Since it’s bundled with its own JRE/JDK, and other components, perhaps they just have it all compiled for M1. I was supposed to have my new MacBook Pro a couple weeks ago, but my company ordered an Intel when I specifically told them NOT to. I need to test these things out before I get them to my developers as well. Plus yes, I want a new toy. I’m waiting for a mini (for myself) to show up at my house, but I waited a long time, and that won’t be here until the end of the month. Grrrr. I really want to test Logic Pro with it!
- needusername 6y ago
  > perhaps they just have it all compiled for M1 That won't work because of the missing W^X support in upstream releases. You need to backport patches.
deleted 6y ago
[deleted]
rk06 6y ago
well here you go: apps are natively compiled for instruction sets eg: x86, x64, ARM64 etc. M1 has an new instruction set. so Apps targeting (x64, x86) need to compile specially to run natively on M1 chip. currently there are few apps which are native as the chip is new. Apple has provided rosetta emulator, which will emulate x86 apps to run on M1 strange, everyone talked rosetta emulator in every single benchmark. NOTE: the above is my current understanding. it may be slightly or grossly incorrect in some areas
- jensv 6y ago
  Anyone know what rewriting for M1 actually entails? Guessing maybe you just recompile all your libraries for M1 and fix any errors and warnings that crop up.
  - jensv 6y ago
    Having said that some consideration to keep in mind: - audio code needs to be optimized for real time thread constrains. Many optimizations usually made by vectorizing rather than threading that would've lead to locks and synchronization not always possible for real-time processing. So not all SIMD code can be compiled just by changing a flag. - machine specific code. While rare. Some companies still got such code for various reasons. And needs more complex transition. - Not all companies were able to obtain DTK. We for example, got our first M1 machine 3 weeks ago. - Backward support. While we'd like to have universal builds, musicians use their systems for years. We still support 10.7. With Big Sur Apple seems to break SHA1 signs making builds from Big Sur work reliably only on 10.11 or newer. (The first release to support SHA256 codesigns) https://news.ycombinator.com/user?id=rock_artist https://news.ycombinator.com/user?id=rock_artist
  - JosephRedfern 6y ago
    Any "hot spots" that have been optimised by writing assembler has to be re-written. Same applies to any dependencies with similar optimisations.
    - danieldk 6y ago
troupe 6y ago
Google Drive Streaming specifically will not work on Apple Silicon yet.

Do Some apps not run on m1? I’ve never heard this.

by rc_mob 6y ago

Do Some apps not run on m1? I’ve never heard this.

I have a PyInstaller-compiled Qt .app that crashes on startup. Weird, because Intel Python in Intel PyCharm is actually working just fine.

The_rationalist 6y ago

Docker for example (might have been fixed now)

bluedino 6y ago
Docker works you just can’t virtualize x86 images
- LukeLambert 6y ago
  The tech preview[1] works and you can run x86 images (though you get a warning from the CLI). [1] https://www.docker.com/blog/download-and-try-the-tech-preview-of-docker-desktop-for-m1/ https://www.docker.com/blog/download-and-try-the-tech-previe...

tonyedgecombe 6y ago

I would assume it's because they depend on the JVM.

millerm 6y ago
X86 JVM runs fine under Rosetta2. Will will be faster now. Looking forward to it!

epilogue 6y ago

As mentioned in the release notes IntelliJ ran under Rosetta 2 previously (Apples x86 to ARM emulation layer) but this new release adds native ARM (Apple Silicon) support.

millerm 6y ago

I believe they’re just referring to the fact it’s native and it’s no longer being utilizing Rosetta2. Since it’s bundled with its own JRE/JDK, and other components, perhaps they just have it all compiled for M1. I was supposed to have my new MacBook Pro a couple weeks ago, but my company ordered an Intel when I specifically told them NOT to. I need to test these things out before I get them to my developers as well. Plus yes, I want a new toy. I’m waiting for a mini (for myself) to show up at my house, but I waited a long time, and that won’t be here until the end of the month. Grrrr. I really want to test Logic Pro with it!

needusername 6y ago
> perhaps they just have it all compiled for M1 That won't work because of the missing W^X support in upstream releases. You need to backport patches.

deleted 6y ago

[deleted]

rk06 6y ago

well here you go: apps are natively compiled for instruction sets eg: x86, x64, ARM64 etc. M1 has an new instruction set. so Apps targeting (x64, x86) need to compile specially to run natively on M1 chip. currently there are few apps which are native as the chip is new. Apple has provided rosetta emulator, which will emulate x86 apps to run on M1 strange, everyone talked rosetta emulator in every single benchmark. NOTE: the above is my current understanding. it may be slightly or grossly incorrect in some areas

jensv 6y ago
Anyone know what rewriting for M1 actually entails? Guessing maybe you just recompile all your libraries for M1 and fix any errors and warnings that crop up.
- jensv 6y ago
  Having said that some consideration to keep in mind: - audio code needs to be optimized for real time thread constrains. Many optimizations usually made by vectorizing rather than threading that would've lead to locks and synchronization not always possible for real-time processing. So not all SIMD code can be compiled just by changing a flag. - machine specific code. While rare. Some companies still got such code for various reasons. And needs more complex transition. - Not all companies were able to obtain DTK. We for example, got our first M1 machine 3 weeks ago. - Backward support. While we'd like to have universal builds, musicians use their systems for years. We still support 10.7. With Big Sur Apple seems to break SHA1 signs making builds from Big Sur work reliably only on 10.11 or newer. (The first release to support SHA256 codesigns) https://news.ycombinator.com/user?id=rock_artist https://news.ycombinator.com/user?id=rock_artist
- JosephRedfern 6y ago
  Any "hot spots" that have been optimised by writing assembler has to be re-written. Same applies to any dependencies with similar optimisations.
  - danieldk 6y ago

troupe 6y ago

Google Drive Streaming specifically will not work on Apple Silicon yet.