Profiler flag (-pg) causing crash while configuring

[raziel-]

Using built-in specs. COLLECT_GCC=/Development/Coding/SDK/gcc/bin/gcc COLLECT_LTO_WRAPPER=/Development/Coding/SDK/gcc/bin/../libexec/gcc/ppc-amigaos/8.3.0/lto-wrapper Target: ppc-amigaos Configured with: /var/lib/jenkins/workspace/native-gcc-8/gcc/repo/configure --with-bugurl=https://github.com/sba1/adtools/issues --with-pkgversion='adtools build 8.3.0' --host=ppc-amigaos --target=ppc-amigaos --disable-nls --prefix=/gcc --with-gmp=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --with-mpfr=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --with-mpc=/var/lib/jenkins/workspace/native-gcc-8/native-build/root-cross --enable-languages=c,c++ --enable-haifa --enable-sjlj-exceptions --disable-libstdcxx-pch --disable-tls --enable-threads=amigaos --enable-lto Thread model: amigaos gcc version 8.3.0 (adtools build 8.3.0)

Adding -pg to the compiler line (configure) makes gcc (within configure, i think) fall over (at least something is crashing).

I know that the crashlog doesn't really show anything obvious related to gcc, but since the only thing i changed was the profiler flag (-pg), i guess it might be gcc to blame. If not, please let me know and i post the bug report elsewhere.

Thank you

PS: Does the profiler need to be explicitely compiled into gcc? Like it was with -flto? Is profiling even supported (yet)? Crashlog_scummvm-conf_2019-05-22_08-25-32.txt

[kas1e]

@Sebastian Is -pg completely unimplemented in our side, or there just bug need to be fixed ? I also tried to use it, but crashes as well

[sba1]

Am 2019-09-21 11:38, schrieb kas1e:

Is -pg completely unimplemented in our side, or there just bug need to be fixed ? I also tried to use it, but crashes as well

I've never looked into this so the effort to enable it is unclear, for me at least. Sorry.

[kas1e]

@sba1

Find out that it crashes when I use -pg and with newlib compile, and with clib2. Just with clib2, you do have AmigaOS native implementation of profile(), so at least that one can be built with -gstabs, to see where exactly it crashes.

Probably some changes in elf.library or in kernel start to cause issues for some time and that profile() code placed inside of clib2's clib2/library/profile_profil.c need to be fixed