From: Jeroen Roovers <jer@gentoo.org>
To: linux-parisc@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>, James.Bottomley@HansenPartnership.com
Subject: GCC 10.1.0 miscompiles PALO IPL, triggers HPMC
Date: Wed, 20 May 2020 10:24:23 +0200 [thread overview]
Message-ID: <20200520102423.40eda06b@wim.jer> (raw)
I compiled PALO 2.12 with GCC 10.1.0 and that triggered an HPMC on a
C8000 when the PDC loads the IPL:
HARD Booted.
<Cpu0> 0000107e00e00000 0000000000000000 CC_BOOT_LAUNCH_IPL_PRI
<Cpu0> 0100142900e00000 fffffff0f0e0ac00 CC_CPU_INTRIGUE_LDB
<Cpu0> 3400082100e00000 0000000000000001 CC_BOOT_BOOT_COMPLETE
<Cpu0> e800009800e00000 00000000000640a8 CC_ERR_CHECK_HPMC
<Cpu0> 37000f7300e00000 8040004000000000 CC_ERR_CPU_CHECK_SUMMARY
<Cpu0> f600105e00e00000 fffffff0f0c00000 CC_MC_HPMC_MONARCH_SELECTED
<Cpu0> 140003b200e00000 000000000000000b CC_ERR_HPMC_STATE_ENTRY
<Cpu0> 400010bd00e00000 0000000000000000 CC_MC_OS_HPMC_CODE_ZERO
<Cpu0> 5600106400e00000 fffffff0f0435110 CC_MC_BR_TO_OS_HPMC_FAILED
https://bugs.gentoo.org/724264
Using built-in specs.
COLLECT_GCC=hppa2.0-unknown-linux-gnu-gcc-10.1.0
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/hppa2.0-unknown-linux-gnu/10.1.0/lto-wrapper
Target: hppa2.0-unknown-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-10.1.0/work/gcc-10.1.0/configure
--host=hppa2.0-unknown-linux-gnu --build=hppa2.0-unknown-linux-gnu
--prefix=/usr --bindir=/usr/hppa2.0-unknown-linux-gnu/gcc-bin/10.1.0
--includedir=/usr/lib/gcc/hppa2.0-unknown-linux-gnu/10.1.0/include
--datadir=/usr/share/gcc-data/hppa2.0-unknown-linux-gnu/10.1.0
--mandir=/usr/share/gcc-data/hppa2.0-unknown-linux-gnu/10.1.0/man
--infodir=/usr/share/gcc-data/hppa2.0-unknown-linux-gnu/10.1.0/info
--with-gxx-include-dir=/usr/lib/gcc/hppa2.0-unknown-linux-gnu/10.1.0/include/g++-v10
--with-python-dir=/share/gcc-data/hppa2.0-unknown-linux-gnu/10.1.0/python
--enable-objc-gc --enable-languages=c,c++,jit,objc,obj-c++,fortran
--enable-obsolete --enable-secureplt --disable-werror
--with-system-zlib --enable-nls --without-included-gettext
--enable-checking=release --with-bugurl=https://bugs.gentoo.org/
--with-pkgversion='Gentoo 10.1.0 p1' --disable-esp
--enable-libstdcxx-time --enable-host-shared --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-multilib --disable-altivec --disable-fixed-point
--enable-libgomp --disable-libmudflap --disable-libssp --disable-libada
--disable-systemtap --disable-vtable-verify --disable-libvtv
--with-zstd --enable-lto --without-isl --enable-default-pie
--disable-default-ssp Thread model: posix Supported LTO compression
algorithms: zlib zstd gcc version 10.1.0 (Gentoo 10.1.0 p1)
palo version 2.12
http://www.parisc-linux.org - Wed May 20 09:34:54 CEST 2020https://rooversj.home.xs4all.nl/gentoo//sys-boot:palo-2.12:20200518-151820.log
The build log[0] showed some seemingly harmless and unrelated warnings
that are new with GCC 10.
Kind regards,
jer
[0] https://rooversj.home.xs4all.nl/gentoo//sys-boot:palo-2.12:20200518-151820.log
reply other threads:[~2020-05-20 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520102423.40eda06b@wim.jer \
--to=jer@gentoo.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.