Unverified Commit 995778bd authored by Kito Cheng's avatar Kito Cheng Committed by GitHub
Browse files

Merge pull request #918 from riscv/bump-gcc

Bump gcc to 11.1
parents b9f21e70 52735e21
Subproject commit 03cb20e5433cd8e65af6a1a6baaf3fe4c72785f6
Subproject commit 5964b5cd72721186ea2195a7be8d40cfe6554023
#
# Upstream regression, PR 86153.
#
FAIL: g++.dg/pr83239.C
#
# Check for nop insns fails due to ".option nopic".
#
FAIL: c-c++-common/patchable_function_entry-decl.c
......@@ -26,10 +22,6 @@ FAIL: gcc.dg/debug/dwarf2/inline5.c
#
XPASS: gcc.dg/graphite/pr69728.c
#
# Upstream regression, PR 94853.
#
FAIL: gfortran.dg/analyzer/pr93993.f90
#
# Upstream regression, PR 90811.
# Patch under review:
# https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543798.html
......
......@@ -12,7 +12,6 @@ FAIL: gcc.dg/cleanup-11.c
#
# XXX: Need review why.
#
FAIL: gfortran.dg/elemental_subroutine_3.f90
FAIL: gfortran.dg/ieee/ieee_6.f90
#
# ieee_1.F90 is a QEMU bug: https://github.com/riscv/riscv-qemu/issues/64
......@@ -22,3 +21,10 @@ FAIL: gfortran.dg/ieee/ieee_1.F90
# Synchronization problem.
#
FAIL: gcc.dg/tree-prof/time-profiler-2.c
#
# TLS related testcase might random fail on qemu
# But it's hard to reproduce and seems only happen on qemu.
# So put those case here for now.
#
FAIL: g++.dg/tls/thread_local4.C
FAIL: g++.dg/tls/thread_local4g.C
#
FAIL: g++.dg/torture/pr86763.C
#
# It's new failed case since GCC 11,
# this case only failed on -O0
# But...I (Kito) don't know fortran too much,
# so put this here for now until someday we have time to
# investigating...
#
FAIL: gfortran.dg/assumed_rank_bounds_3.f90
......@@ -13,3 +13,12 @@ FAIL: gcc.c-torture/execute/printf-2.c
# Missing dg-require-effective-target shared
#
FAIL: g++.dg/lto/pr87906 cp_lto_pr87906_0.o-cp_lto_pr87906_1.o link, -O -fPIC -flto
#
# -lc not enough to link final executable for newlib.
#
FAIL: g++.dg/abi/pure-virtual1.C
#
# newlib header issue, `reent.h`has complication warning when compile
# with `-Wall`
#
FAIL: g++.dg/warn/Wstringop-overflow-6.C
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment