public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/115322] New: SPEC2006 403.gcc internal error
@ 2024-06-03 6:09 sundongya at nucleisys dot com
2024-06-03 6:16 ` [Bug target/115322] " pinskia at gcc dot gnu.org
2024-06-04 8:27 ` sundongya at nucleisys dot com
0 siblings, 2 replies; 3+ messages in thread
From: sundongya at nucleisys dot com @ 2024-06-03 6:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115322
Bug ID: 115322
Summary: SPEC2006 403.gcc internal error
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: sundongya at nucleisys dot com
Target Milestone: ---
Hi,
GCC version:
gcc version 14.1.1 20240507 (g7e8fae89f)
Build SPEC2006 cfg1:
# Compiler selection
CC = riscv64-unknown-linux-gnu-gcc
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m1
CXX = riscv64-unknown-linux-gnu-g++
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m1
FC = riscv64-unknown-linux-gnu-gfortran
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m1
# Optimization
default=base=default=default:
COPTIMIZE = -Ofast -flto
CXXOPTIMIZE = -Ofast -flto
FOPTIMIZE = -Ofast -flto
# 32/64 bit Portability Flags - all
default=base=default=default:
PORTABILITY = -Wno-error=implicit-int
-Wno-error=implicit-function-declaration
-Wno-error=declaration-missing-parameter-type -Wno-error=return-mismatch
-Wno-error=int-conversion -Wno-error=incompatible-pointer-types -DSPEC_CPU_LP64
Build SPEC2006 cfg2:
# Compiler selection
CC = riscv64-unknown-linux-gnu-gcc
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m4
CXX = riscv64-unknown-linux-gnu-g++
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m4
FC = riscv64-unknown-linux-gnu-gfortran
-march=rv64imafdcv_zba_zbb_zbc_zbs_zvl128b -mabi=lp64d -static
-mrvv-vector-bits=zvl -mrvv-max-lmul=m4
# Optimization
default=base=default=default:
COPTIMIZE = -Ofast -flto
CXXOPTIMIZE = -Ofast -flto
FOPTIMIZE = -Ofast -flto
# 32/64 bit Portability Flags - all
default=base=default=default:
PORTABILITY = -Wno-error=implicit-int
-Wno-error=implicit-function-declaration
-Wno-error=declaration-missing-parameter-type -Wno-error=return-mismatch
-Wno-error=int-conversion -Wno-error=incompatible-pointer-types -DSPEC_CPU_LP64
After successfully compiling SPEC2006 using the above configuration, the
following problem will occur in 403.gcc when running the intspeed/test data
set.
gcc_base.riscv: internal error: 4
It is possible that you may be trying to use SPEC's version of gcc
without first defining the appropriate flags. Please check the flags
that are in the config files from recently-published results on your
platform, and check that you are using an up-to-date compiler. If
you still need help, please contact SPEC, reporting your hw/os
platform, your compiler version, and your compilation flags.
Contact SPEC at <URL:http://www.spec.org/>
Similar error will occur when running the simulation in user mode in qemu. The
running command is as follows:
# qemu version
qemu-riscv64 version 8.2.93 (v9.0.0-rc3-5-g824ebb92c3)
#running command
qemu-riscv64 -cpu rv64,v=true,vext_spec=v1.0,zicond=true ./gcc_base.riscv
cccp.in -o cccp.s
cccp.in:1679: internal error: 11
It is possible that you may be trying to use SPEC's version of gcc
without first defining the appropriate flags. Please check the flags
that are in the config files from recently-published results on your
platform, and check that you are using an up-to-date compiler. If
you still need help, please contact SPEC, reporting your hw/os
platform, your compiler version, and your compilation flags.
Contact SPEC at <URL:http://www.spec.org/>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/115322] SPEC2006 403.gcc internal error
2024-06-03 6:09 [Bug c/115322] New: SPEC2006 403.gcc internal error sundongya at nucleisys dot com
@ 2024-06-03 6:16 ` pinskia at gcc dot gnu.org
2024-06-04 8:27 ` sundongya at nucleisys dot com
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-06-03 6:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115322
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Component|c |target
Last reconfirmed| |2024-06-03
Target| |riscv
Status|UNCONFIRMED |WAITING
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Does adding -fno-strict-aliasing help?
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/115322] SPEC2006 403.gcc internal error
2024-06-03 6:09 [Bug c/115322] New: SPEC2006 403.gcc internal error sundongya at nucleisys dot com
2024-06-03 6:16 ` [Bug target/115322] " pinskia at gcc dot gnu.org
@ 2024-06-04 8:27 ` sundongya at nucleisys dot com
1 sibling, 0 replies; 3+ messages in thread
From: sundongya at nucleisys dot com @ 2024-06-04 8:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115322
--- Comment #2 from 孙东亚 <sundongya at nucleisys dot com> ---
(In reply to Andrew Pinski from comment #1)
> Does adding -fno-strict-aliasing help?
After adding this compilation option, the same error will still be reported
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-04 8:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-03 6:09 [Bug c/115322] New: SPEC2006 403.gcc internal error sundongya at nucleisys dot com
2024-06-03 6:16 ` [Bug target/115322] " pinskia at gcc dot gnu.org
2024-06-04 8:27 ` sundongya at nucleisys dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).