Changes between Version 2 and Version 3 of Ticket #58442, comment 39
- Timestamp:
- May 10, 2019, 12:37:08 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #58442, comment 39
v2 v3 22 22 MacOS **10.7**? Are you validating under 10.14.x using Xcode-10.2.x? If not, I'd say that explains why you aren't catching this crash. Xcode-10.2 is quite different in what it allows and what it fails than the previous versions, at least in my experience. 23 23 24 Also, as I'm working with crypto code that tries to squeeze an extra bit of performance by utilizing inline assembly (I'm one of the maintainers of Crypto++ https://en.wikipedia.org/wiki/Crypto%2B%2B library), I'm trying to make sure it compiles with all the compilers available on MacOS. I noticed that the only way to get Macports GCC to compile with inline assembly is to make it invoke Xcode assembler via {{{-Wa,-q}}}. We're also using {{{export AS_INTEGRATED_ASSEMBLER=1}}}.24 Also, as I'm working with crypto code that tries to squeeze an extra bit of performance by utilizing inline assembly (I'm one of the maintainers of Crypto++ https://en.wikipedia.org/wiki/Crypto%2B%2B library), I'm trying to make sure it compiles with all the compilers available on MacOS. I noticed that the only way to get Macports GCC to compile code with inline assembly is to make it invoke Xcode assembler via {{{-Wa,-q}}}. We're also using {{{export AS_INTEGRATED_ASSEMBLER=1}}}. 25 25 I'd just stick with Xcode, but it's GCC sucks even more, and it's very outdated besides. So, for a decent GCC have to use Macports port. 26 26