CI: use GCC10 on ppc too

We were still using GCC9, because GCC10 was failing.

* .travis.yml (PPC64le): Use GCC10.
While at it, use -O2 instead of -O3: it's certainly nicer for the
CPUs, and allows to test different sets of compiler flags (we use -O3
in several other configurations).
This commit is contained in:
Akim Demaille
2020-06-06 07:45:10 +02:00
parent b1327c56f7
commit 2101b0e210

View File

@@ -135,7 +135,7 @@ jobs:
packages: packages:
- intel-oneapi-icc - intel-oneapi-icc
- name: "ARM64: GCC 10 -O3 part 1" - name: "ARM64: GCC 10 -O2 part 1"
stage: check stage: check
os: linux os: linux
arch: arm64 arch: arm64
@@ -144,12 +144,10 @@ jobs:
env: env:
- CC=gcc-10 - CC=gcc-10
- CXX=g++-10 - CXX=g++-10
- CONFIGUREFLAGS='CPPFLAGS=-DNDEBUG CFLAGS=-O3 CXXFLAGS=-O3' - CONFIGUREFLAGS='CPPFLAGS=-DNDEBUG CFLAGS=-O2 CXXFLAGS=-O2'
- PART=1 - PART=1
# GCC10 on PPC seems to be buggy. - name: "PPC64le: GCC 10 -O2 part 1"
# E.g., https://travis-ci.org/github/akimd/bison/jobs/687812428.
- name: "PPC64le: GCC 9 part 1"
stage: check stage: check
os: linux os: linux
arch: ppc64le arch: ppc64le
@@ -159,14 +157,14 @@ jobs:
sources: sources:
# See https://github.com/travis-ci/apt-source-safelist/issues/410. # See https://github.com/travis-ci/apt-source-safelist/issues/410.
- sourceline: 'ppa:ubuntu-toolchain-r/test' - sourceline: 'ppa:ubuntu-toolchain-r/test'
packages: g++-9 packages: g++-10
env: env:
- CC=gcc-9 - CC=gcc-10
- CXX=g++-9 - CXX=g++-10
- CONFIGUREFLAGS='CFLAGS=-O3 CXXFLAGS=-O3' - CONFIGUREFLAGS='CFLAGS=-O2 CXXFLAGS=-O2'
- PART=1 - PART=1
- name: "s390x: GCC 10 part 1" - name: "s390x: GCC 10 -O2 part 1"
stage: check stage: check
os: linux os: linux
arch: s390x arch: s390x
@@ -175,7 +173,7 @@ jobs:
env: env:
- CC=gcc-10 - CC=gcc-10
- CXX=g++-10 - CXX=g++-10
- CONFIGUREFLAGS='CFLAGS=-O3 CXXFLAGS=-O3' - CONFIGUREFLAGS='CFLAGS=-O2 CXXFLAGS=-O2'
- PART=1 - PART=1
## ----- ## ## ----- ##