Bug#943796: gcc-9: FTBFS on hppa - ld cannot find -latomic

2019-10-29 Thread Matthias Klose

On 29.10.19 23:26, John David Anglin wrote:

/usr/bin/hppa-linux-gnu-ld: cannot find -latomic
collect2: error: ld returned 1 exit status


yes, fixed in the VCS



Bug#943796: gcc-9: FTBFS on hppa - ld cannot find -latomic

2019-10-29 Thread John David Anglin
Source: gcc-9
Version: 9.2.1-15
Severity: normal

Dear Maintainer,

The build failed with the following error:

make[6]: Entering directory '/<>/build/hppa-linux-gnu/libgnatvsn'
/bin/mkdir -p '/<>/debian/tmp/usr/lib/ada/adalib/gnatvsn'
/usr/bin/install -c -m 444 .libs/*.ali 
'/<>/debian/tmp/usr/lib/ada/adalib/gnatvsn'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib'
 /bin/bash ./libtool   --mode=install /usr/bin/install -c   libgnatvsn.la 
'/<>/debian/tmp/usr/lib'
libtool: install: warning: relinking `libgnatvsn.la'
libtool: install: (cd /<>/build/hppa-linux-gnu/libgnatvsn; 
/bin/bash /<>/build/hppa-linux-gnu/libgnatvsn/libtool  --tag CC 
--mode=relink /<>/build/./gcc/xgcc -B/<>/build/./gcc/ 
-B/usr/hppa-linux-gnu/bin/ -B/usr/hppa-linux-gnu/lib/ -isystem 
/usr/hppa-linux-gnu/include -isystem /usr/hppa-linux-gnu/sys-include -isystem 
/<>/build/sys-include -fchecking=1 -mdisable-indexing -g -O2 
-version-info 9 -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
-Wl,--no-undefined -Wl,-z,relro -o libgnatvsn.la -rpath /usr/lib 
libgnatvsn_la-link.lo libgnatvsn_la-version.lo -L../libada/adalib -lgnat-9 
aspects.lo atree.lo binderr.lo butil.lo casing.lo csets.lo debug.lo einfo.lo 
elists.lo fname.lo get_scos.lo gnatvsn.lo krunch.lo lib.lo namet.lo nlists.lo 
opt.lo output.lo put_scos.lo repinfo.lo repinfo-input.lo scans.lo scos.lo 
sem_aux.lo sinfo.lo sinput.lo sinput-c.lo stand.lo stringt.lo table.lo 
tempdir.lo tree_in.lo tree_io.lo types.lo uintp.lo uname.lo urealp.lo 
widechar.lo xutil.lo snames.lo alloc.lo hostparm.lo rident.lo 
.././libatomic/libatomic.la -inst-prefix-dir /<>/debian/tmp)
libtool: relink: /<>/build/./gcc/xgcc 
-B/<>/build/./gcc/ -B/usr/hppa-linux-gnu/bin/ 
-B/usr/hppa-linux-gnu/lib/ -isystem /usr/hppa-linux-gnu/include -isystem 
/usr/hppa-linux-gnu/sys-include -isystem /<>/build/sys-include   
-fchecking=1 -shared  -fPIC -DPIC  .libs/libgnatvsn_la-link.o 
.libs/libgnatvsn_la-version.o .libs/aspects.o .libs/atree.o .libs/binderr.o 
.libs/butil.o .libs/casing.o .libs/csets.o .libs/debug.o .libs/einfo.o 
.libs/elists.o .libs/fname.o .libs/get_scos.o .libs/gnatvsn.o .libs/krunch.o 
.libs/lib.o .libs/namet.o .libs/nlists.o .libs/opt.o .libs/output.o 
.libs/put_scos.o .libs/repinfo.o .libs/repinfo-input.o .libs/scans.o 
.libs/scos.o .libs/sem_aux.o .libs/sinfo.o .libs/sinput.o .libs/sinput-c.o 
.libs/stand.o .libs/stringt.o .libs/table.o .libs/tempdir.o .libs/tree_in.o 
.libs/tree_io.o .libs/types.o .libs/uintp.o .libs/uname.o .libs/urealp.o 
.libs/widechar.o .libs/xutil.o .libs/snames.o .libs/alloc.o .libs/hostparm.o 
.libs/rident.o   -L/<>/build/hppa-linux-gnu/libada/adalib -lgnat-9 
-L/<>/debian/tmp/usr/lib -L/usr/lib -latomic  -mdisable-indexing 
-Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
-Wl,--no-undefined -Wl,-z -Wl,relro   -pthread -Wl,-soname -Wl,libgnatvsn.so.9 
-o .libs/libgnatvsn.so.9.0.0
/usr/bin/hppa-linux-gnu-ld: cannot find -latomic
collect2: error: ld returned 1 exit status
libtool: install: error: relink `libgnatvsn.la' with the above command before 
installing it
make[6]: *** [Makefile:552: install-libLTLIBRARIES] Error 1

The hppa architecture has a non empty libatomic that needs to be linked
against for atomic support.

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=gcc-9=hppa=9.2.1-15=1572353329=0

Regards,
Dave Anglin


-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.150+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information



Processed: reassign 943401 to g++-9, found 943401 in 9.2.1-12

2019-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 943401 g++-9
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
Bug reassigned from package 'gcc-9' to 'g++-9'.
No longer marked as found in versions gcc-9/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> found 943401 9.2.1-12
Bug #943401 [g++-9] libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
Marked as found in versions gcc-9/9.2.1-12.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
943401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc) 9.2.1-12 ((

2019-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 943401 gcc-9
Bug #943401 [libstdc++6] libreoffice C++ Unit tests failing since 9.2.1-12 
((Failure instantiating exceptionprotector)
Bug reassigned from package 'libstdc++6' to 'gcc-9'.
No longer marked as found in versions gcc-9/9.2.1-12.
Ignoring request to alter fixed versions of bug #943401 to the same values 
previously set
> found 943401 9.2.1-12
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure 
instantiating exceptionprotector)
Marked as found in versions gcc-9/9.2.1-12.
> retitle 943401 libreoffice C++ Unit tests failing when built with gcc >= 
> 9.2.1-12 (Failure instantiating exceptionprotector)
Bug #943401 [gcc-9] libreoffice C++ Unit tests failing since 9.2.1-12 ((Failure 
instantiating exceptionprotector)
Changed Bug title to 'libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)' from 'libreoffice C++ Unit 
tests failing since 9.2.1-12 ((Failure instantiating exceptionprotector)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
943401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



libreoffice C++ Unit tests failing when built with gcc >= 9.2.1-12 (Failure instantiating exceptionprotector) (was: Re: Bug#943401: libreoffice C++ Unit tests failing since gcc) 9.2.1-12 ((Failure ins

2019-10-29 Thread Rene Engelhard
reassign 943401 gcc-9
found 943401 9.2.1-12
retitle 943401 libreoffice C++ Unit tests failing when built with gcc >= 
9.2.1-12 (Failure instantiating exceptionprotector)
thanks

On Tue, Oct 29, 2019 at 03:09:50PM +0100, Vincent Lefevre wrote:
> 1. Build smoketest with the old g++-9 / libstdc++6.

In testing against 6.3.2 there:

== Starting smoketest with 1 job against 
path:/usr/lib/libreoffice/program/soffice ==
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  touch 
$W/Headers/CppunitTest/libtest_smoketest.so
[CXX] smoketest/smoketest_too.cxx
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  mkdir -p $W/CxxObject/smoketest/ 
$W/Dep/CxxObject/smoketest/ && cd 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 &&
x86_64-linux-gnu-g++ -DBOOST_ERROR_CODE_HEADER_ONLY 
-DBOOST_SYSTEM_NO_DEPRECATED -DCPPU_ENV=gcc3 -DLINUX -DNDEBUG 
-DOSL_DEBUG_LEVEL=0 -DUNIX -DUNX -DX86_64 -D_FORTIFY_SOURCE=2 -D_PTHREADS 
-D_REENTRANT -Wdate-time   -DCPPUNIT_PLUGIN_EXPORT='extern "C" 
SAL_DLLPUBLIC_EXPORT'   -fvisibility=hidden-Wall -Wno-missing-braces 
-Wnon-virtual-dtor -Wendif-labels -Wextra -Wundef -Wunreachable-code 
-Wunused-macros -finput-charset=UTF-8 -fmessage-length=0 -fno-common -pipe  
-Wno-maybe-uninitialized -Wduplicated-cond -Wlogical-op -Wshift-overflow=2 
-Wunused-const-variable=1 -Wno-cast-function-type -fvisibility-inlines-hidden 
-fPIC -Wshadow -Woverloaded-virtual -std=gnu++2a -pthread   -DEXCEPTIONS_ON 
-fexceptions -fno-enforce-eh-specs -g -O2 
-fdebug-prefix-map=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2=.
 -fstack-protector-strong -Wformat -Werror=format-security
-DLIBO_INTERNAL_ONLY  -c $S/smoketest/smoketest_too.cxx -o 
$W/CxxObject/smoketest/smoketest_too.o  -I$S/include  
-I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
-I$S/config_host   -I/usr/include  -I$W/UnoApiHeadersTarget/udkapi/normal 
-I$W/UnoApiHeadersTarget/offapi/normal   
[LNK] CppunitTest/libtest_smoketest.so
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&  x86_64-linux-gnu-g++ -pthread 
-shared -Wl,-z,noexecstack   -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' 
-Wl,-rpath-link,$I/program -Wl,-z,defs -Wl,-rpath-link,/lib:/usr/lib 
-Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,-Bsymbolic-functions 
-L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$S/instdir/program  
-L$S/instdir/program  -L$W/LinkTarget/Library -Wl,-z,relro
$W/CxxObject/smoketest/smoketest_too.o  -Wl,--start-group-lcppunit   
-Wl,--end-group -Wl,--no-as-needed -luno_cppu -luno_cppuhelpergcc3 -luno_sal 
-lunotest  -o $W/LinkTarget/CppunitTest/libtest_smoketest.so 
TEMPFILE=/tmp/gbuild.ptBn7D &&  mv ${TEMPFILE} 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/LinkTarget/CppunitTest/libtest_smoketest.so.objectlist
rm -rf 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/qadevOOo/qa/registrymodifications.xcu
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/CustomTarget/smoketest/user
mkdir -p 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/
touch 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.prepare
[ZIP] smoketestdoc
S=/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2 && 
I=/usr/lib/libreoffice && W=$S/workdir &&   RESPONSEFILE=/tmp/gbuild.jGkR3E && 
cd $S/smoketest/data && cat ${RESPONSEFILE} | tr "[:space:]" "\n" | zip  -D 
-@rX --filesync --must-match $W/Zip/smoketestdoc.zip && rm -f ${RESPONSEFILE} 
&& touch $W/Zip/smoketestdoc.zip   
  adding: mimetype (stored 0%)
  adding: content.xml (deflated 77%)
  adding: meta.xml (deflated 55%)
  adding: settings.xml (deflated 80%)
  adding: styles.xml (deflated 77%)
  adding: META-INF/manifest.xml (deflated 73%)
  adding: Basic/script-lc.xml (deflated 47%)
  adding: Basic/Standard/script-lb.xml (deflated 52%)
  adding: Basic/Standard/Events.xml (deflated 54%)
  adding: Basic/Standard/Global.xml (deflated 78%)
  adding: Basic/Standard/Test_10er.xml (deflated 80%)
  adding: Basic/Standard/Test_DB.xml (deflated 68%)
  adding: Basic/Standard/Test_Ext.xml (deflated 47%)
  adding: Dialogs/dialog-lc.xml (deflated 47%)
  adding: Dialogs/Standard/dialog-lb.xml (deflated 47%)
  adding: Dialogs/Standard/OptionsDlg.xml (deflated 73%)
cp 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.zip
 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-6.3.2.2/workdir/Zip/smoketestdoc.sxw
[CUT] 

Results for 9.2.1 20191027 (Debian 9.2.1-15) testsuite on s390x-ibm-linux-gnu

2019-10-29 Thread Matthias Klose
LAST_UPDATED: Sun Oct 27 12:53:25 UTC 2019 (revision 277486)

=== acats tests ===

=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is s390x-ibm-linux-gnu

=== g++ tests ===


Running target unix
FAIL: c-c++-common/asan/global-overflow-1.c   -O2  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O3 -g  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -Os  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O0  execution test
FAIL: g++.dg/asan/function-argument-3.C   -O1  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O3 -g  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -Os  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O3 -g  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -Os  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: c-c++-common/Wattributes.c  -std=gnu++98  (test for errors, line 404)
FAIL: c-c++-common/Wattributes.c  -std=gnu++14  (test for errors, line 404)
FAIL: c-c++-common/Wattributes.c  -std=gnu++17  (test for errors, line 404)
FAIL: g++.dg/gomp/tls-5.C  -std=c++14  scan-assembler-not .data
FAIL: g++.dg/gomp/tls-5.C  -std=c++17  scan-assembler-not .data
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  line 23 p == 40
FAIL: g++.dg/tls/thread_local7.C  -std=c++14  scan-assembler-not .data
FAIL: g++.dg/tls/thread_local7.C  -std=c++17  scan-assembler-not .data
FAIL: g++.dg/tls/thread_local7g.C  -std=c++14  scan-assembler-not .data
FAIL: g++.dg/tls/thread_local7g.C  -std=c++17  scan-assembler-not .data

=== g++ Summary for unix ===

# of expected passes133008
# of unexpected failures29
# of expected failures  524
# of unsupported tests  6501

Running target unix/-fstack-protector
FAIL: c-c++-common/asan/global-overflow-1.c   -O2  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O3 -g  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -Os  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: c-c++-common/asan/global-overflow-1.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O0  execution test
FAIL: g++.dg/asan/function-argument-3.C   -O1  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O3 -g  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -Os  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: g++.dg/asan/function-argument-3.C   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O3 -g  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -Os  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  output pattern test
FAIL: g++.dg/asan/large-func-test-1.C   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  output pattern test
FAIL: c-c++-common/Wattributes.c  -std=gnu++98  (test for errors, line 404)
FAIL: c-c++-common/Wattributes.c  -std=gnu++14  (test for errors, line 404)
FAIL: c-c++-common/Wattributes.c  -std=gnu++17  (test for errors, line 404)
FAIL: g++.dg/gomp/tls-5.C  -std=c++14  scan-assembler-not .data
FAIL: g++.dg/gomp/tls-5.C  -std=c++17  scan-assembler-not .data
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  line 23 p == 40
FAIL: g++.dg/tls/thread_local7.C  -std=c++14  scan-assembler-not .data
FAIL: 

Results for 9.2.1 20191027 (Debian 9.2.1-15) testsuite on arm-unknown-linux-gnueabi

2019-10-29 Thread Matthias Klose
LAST_UPDATED: Sun Oct 27 12:53:25 UTC 2019 (revision 277486)

Native configuration is arm-unknown-linux-gnueabi

=== libatomic tests ===


Running target unix

=== libatomic Summary ===

# of expected passes44
# of unsupported tests  5
=== libffi tests ===


Running target unix

=== libffi Summary ===

# of expected passes2214
=== libgo tests ===


Running target unix
FAIL: os
FAIL: os/signal
FAIL: runtime
FAIL: runtime/pprof
FAIL: sync/atomic

=== libgo Summary ===

# of expected passes179
# of unexpected failures5
/build/gcc-9-pENaVc/gcc-9-9.2.1/build/./gcc/gccgo version 9.2.1 20191027 
(Debian 9.2.1-15)

=== libgomp tests ===


Running target unix

=== libgomp Summary ===

# of expected passes6357
# of expected failures  4
# of unsupported tests  422
=== libphobos tests ===


Running target unix
FAIL: libphobos.phobos/std/math.d execution test
WARNING: libphobos.phobos/std/range/package.d (test for excess errors) program 
timed out.
FAIL: libphobos.phobos/std/range/package.d (test for excess errors)
UNRESOLVED: libphobos.phobos/std/range/package.d compilation failed to produce 
executable
FAIL: libphobos.phobos/std/zip.d execution test
FAIL: libphobos.phobos_shared/std/math.d execution test
WARNING: libphobos.phobos_shared/std/range/package.d (test for excess errors) 
program timed out.
FAIL: libphobos.phobos_shared/std/range/package.d (test for excess errors)
UNRESOLVED: libphobos.phobos_shared/std/range/package.d compilation failed to 
produce executable
FAIL: libphobos.phobos_shared/std/zip.d execution test

=== libphobos Summary ===

# of expected passes744
# of unexpected failures6
# of unresolved testcases   2
# of unsupported tests  2
=== libstdc++ tests ===


Running target unix
FAIL: 22_locale/time_get/get_time/char/2.cc execution test
FAIL: 22_locale/time_get/get_time/char/wrapped_env.cc execution test
FAIL: 22_locale/time_get/get_time/char/wrapped_locale.cc execution test
FAIL: 22_locale/time_get/get_time/wchar_t/2.cc execution test
FAIL: 22_locale/time_get/get_time/wchar_t/wrapped_env.cc execution test
FAIL: 22_locale/time_get/get_time/wchar_t/wrapped_locale.cc execution test
FAIL: libstdc++-prettyprinters/80276.cc whatis p4
FAIL: libstdc++-prettyprinters/80276.cc whatis p4

=== libstdc++ Summary ===

# of expected passes13461
# of unexpected failures8
# of expected failures  78
# of unsupported tests  371
=== acats tests ===

=== acats Summary ===
# of expected passes2320
# of unexpected failures0

=== g++ tests ===


Running target unix
FAIL: g++.dg/other/anon5.C  -std=gnu++98 (test for excess errors)
FAIL: g++.dg/other/anon5.C  -std=gnu++14 (test for excess errors)
FAIL: g++.dg/other/anon5.C  -std=gnu++17 (test for excess errors)
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  line 23 p == 40
FAIL: g++.dg/lto/pr65276 cp_lto_pr65276_0.o-cp_lto_pr65276_1.o link, -flto -O0 
-std=c++11
FAIL: g++.dg/vect/pr87914.cc  -std=c++98 execution test
FAIL: g++.dg/vect/pr87914.cc  -std=c++14 execution test
FAIL: g++.dg/vect/pr87914.cc  -std=c++17 execution test

=== g++ Summary ===

# of expected passes130481
# of unexpected failures10
# of expected failures  511
# of unsupported tests  6555
/build/gcc-9-pENaVc/gcc-9-9.2.1/build/gcc/xg++  version 9.2.1 20191027 (Debian 
9.2.1-15) 

=== gcc tests ===


Running target unix
FAIL: gcc.dg/gimplefe-28.c (internal compiler error)
FAIL: gcc.dg/gimplefe-28.c (test for excess errors)
FAIL: gcc.dg/ira-shrinkwrap-prep-1.c scan-rtl-dump pro_and_epilogue "Performing 
shrink-wrapping"
FAIL: gcc.dg/graphite/interchange-1.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-10.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-11.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-3.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-4.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-7.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-9.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/uns-interchange-9.c scan-tree-dump graphite "tiled"
XPASS: gcc.dg/guality/example.c   -O0  execution test
XPASS: gcc.dg/guality/example.c   -O1  -DPREVENT_OPTIMIZATION  execution test
XPASS: gcc.dg/guality/example.c   -O2  -DPREVENT_OPTIMIZATION  execution test
XPASS: gcc.dg/guality/example.c   -Os  -DPREVENT_OPTIMIZATION  execution test
XPASS: 

Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread rene . engelhard
Hi,

Am 29. Oktober 2019 15:09:50 MEZ schrieb Vincent Lefevre :
>On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
>> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre
>:
>> >In case makefile magic triggers some rebuild, you can also run the
>> >generated executable directly (with the right environment variables,
>> >in case this matters). If the programs honors the system ABI, this
>> >is allowed, and you'll effectively test the new libstdc++6.
>> 
>> No, if the rebuild rebuilds cppunittester or one of the
>> exceptionprotectors or the smoketest so or similar we are at the
>> same situation as with the autopkgtest (that's what it builds) and
>> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
>> test are an executable it's a executable with gazillions of .sos.
>
>I meant running the generated program (smoketest) without rebuilding
>it:

Smoketest is not a program but also a libsmoketest.so "ran" by cppunittester.

>1. Build smoketest with the old g++-9 / libstdc++6.
>2. Upgrade g++-9 / libstdc++6.
>3. Run smoketest directly.

That would need to copy the longish command from the old log, but yeah.

>(I assume that the smoketest executable does not invoke g++-9 to
>rebuild things on the fly.)

No, but make check in smokest might rebuild stuff. That was what I was aiming 
at. This already happens in "normal" builds.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread Vincent Lefevre
On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
> >In case makefile magic triggers some rebuild, you can also run the
> >generated executable directly (with the right environment variables,
> >in case this matters). If the programs honors the system ABI, this
> >is allowed, and you'll effectively test the new libstdc++6.
> 
> No, if the rebuild rebuilds cppunittester or one of the
> exceptionprotectors or the smoketest so or similar we are at the
> same situation as with the autopkgtest (that's what it builds) and
> are not sure whether it's g++-9 or libstdc++6. Neither LO nor the
> test are an executable it's a executable with gazillions of .sos.

I meant running the generated program (smoketest) without rebuilding
it:

1. Build smoketest with the old g++-9 / libstdc++6.
2. Upgrade g++-9 / libstdc++6.
3. Run smoketest directly.

(I assume that the smoketest executable does not invoke g++-9 to
rebuild things on the fly.)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread rene . engelhard
Hi,

Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
>In case makefile magic triggers some rebuild, you can also run the
>generated executable directly (with the right environment variables,
>in case this matters). If the programs honors the system ABI, this
>is allowed, and you'll effectively test the new libstdc++6.

No, if the rebuild rebuilds cppunittester or one of the exceptionprotectors or 
the smoketest so or similar we are at the same situation as with the 
autopkgtest (that's what it builds) and are not sure whether it's g++-9 or 
libstdc++6. Neither LO nor the test are an executable it's a executable with 
gazillions of .sos.

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread Vincent Lefevre
On 2019-10-29 11:52:55 +0100, rene.engelh...@mailbox.org wrote:
> Hi again,
> 
> Am 29. Oktober 2019 11:26:41 MEZ schrieb rene.engelh...@mailbox.org:
> >Hi,
> >
> >Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre
> >:
> >> If you build LO
> >>with an older gcc-9 version, upgrade libstdc++6, and run the test
> >>again (without rebuilding it), does it fail?
> >
> >This is impossible. This is a C++ unit test and the stuff assumes too
> >much of the build tree. You need to actually build the test libs etc to
> >run it. 
> >
> >That is why autopkgtest does only smoketest [...]
> 
> Well, thinking about it it might be possible. Build on testing,
> debian/tests/smoketest, dist-upgrade to did and rerun it and hope
> some makefile magic doesn't trigger some rebuild...

In case makefile magic triggers some rebuild, you can also run the
generated executable directly (with the right environment variables,
in case this matters). If the programs honors the system ABI, this
is allowed, and you'll effectively test the new libstdc++6.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread rene . engelhard
Hi again,

Am 29. Oktober 2019 11:26:41 MEZ schrieb rene.engelh...@mailbox.org:
>Hi,
>
>Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre
>:
>> If you build LO
>>with an older gcc-9 version, upgrade libstdc++6, and run the test
>>again (without rebuilding it), does it fail?
>
>This is impossible. This is a C++ unit test and the stuff assumes too
>much of the build tree. You need to actually build the test libs etc to
>run it. 
>
>That is why autopkgtest does only smoketest [...]

Well, thinking about it it might be possible. Build on testing, 
debian/tests/smoketest, dist-upgrade to did and rerun it and hope some makefile 
magic doesn't trigger some rebuild...

The smokest (except the cppunit blurb)  just does "run lo, open 
smoketestdoc.sxw, run some macros to test basic stuff".

Will try...

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread rene . engelhard
Hi,

Am 29. Oktober 2019 10:59:07 MEZ schrieb Vincent Lefevre :
> If you build LO
>with an older gcc-9 version, upgrade libstdc++6, and run the test
>again (without rebuilding it), does it fail?

This is impossible. This is a C++ unit test and the stuff assumes too much of 
the build tree. You need to actually build the test libs etc to run it. 

That is why autopkgtest does only smoketest instead of all c++ unit tests even 
though the latter would be helpful.
Tried to decouple it once but failed as it always either wanted something 
present it write in the "instdir".

Regards

Rene

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Re: Bug#943401: libreoffice C++ Unit tests failing since gcc 9.2.1-12 ((Failure instantiating exceptionprotector)

2019-10-29 Thread Vincent Lefevre
On 2019-10-28 23:34:11 +0100, Rene Engelhard wrote:
> You like to make other people bad where this is not the case. In this
> case this is not a LO bug since the exact same LO version worked until
> said gcc upload.

If the LO code has some undefined behavior, it could also be a LO bug
triggered by some new optimization or other change in the compiler.

That said, when seeing a new failure with a new GCC version for MPFR,
in (almost) all cases, this was due to a bug in GCC (after I spent
some time to build a simple testcase). But note that I also test MPFR
with sanitizer options, so that if there is some UB in MPFR, I would
probably notice it first.

I notice that this bug is assigned to libstdc++6. Do you think that
it is a library issue rather than a compiler issue? If you build LO
with an older gcc-9 version, upgrade libstdc++6, and run the test
again (without rebuilding it), does it fail?

If this is due to the compilation step, I would suggest to check LO
with sanitizer options. I also notice that the logs show the that
-fno-enforce-eh-specs option is used, which might also hide issues,
I suppose.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)