Macos ppcx64 throwing exception when compiling tests/test/tobjc10.pp
## Summary I built fpc trunk (9c7d151) on macos x86_64 and then used compiler/ppcx64 to build tests/test/tobjc10.pp. Compilation fails with following message: tobjc10.pp(13,60) Error: Compilation raised exception internally Fatal: Compilation aborted An unhandled exception occurred at $000000010EC316CC: EAccessViolation: Access violation $000000010EC316CC $000000010ECC1D52<!-- Summarize the bug encountered concisely --> ## System Information <!-- The more information are provided the easier it is to replicate the bug --> - **Operating system:** MacOS<!-- Windows, Linux (if possible, also name the distro), FreeBSD, Android, ... --> - **Processor architecture:** x86_64<!-- x86, x86-64, ARM, AARCH64, AVR, RISC-V, PowerPC, ... --> - **Compiler version:** trunk 9c7d151<!-- 3.2, 3.2.2, 3.3, trunk, beta, ... (if possible, give also the git hash) --> - **Device:** <!-- Computer, Tablet, Mobile, Amiga, Microcontroller, ... --> ## Steps to reproduce build ppcx64 on macos x86_64 then compiler/ppcx64 tests/test/tobjc10.pp <!-- How one can reproduce the issue - this is very important! --> ## Example Project <!-- If possible, please create an example project that exhibits the problematic behavior, and link to it here in the bug report. --> ## What is the current bug behavior? compile errors out with raised exception internally error <!-- What actually happens --> ## What is the expected (correct) behavior? file should compile without error <!-- What you should see instead --> ## Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise. You can also use syntax highlighting for Pascal with: ```pascal the code``` For more information see https://docs.gitlab.com/ee/user/markdown.html --> ## Possible fixes - issue is related to objcprotocol() keyword - appeared after trunk version 73185e8 (8/25/2022) <!-- If you can, link to the line of code that might be responsible for the problem -->
issue