Bug#1016936: dwz: fails while building assaultcube

2023-02-20 Thread Alberto Garcia
On Wed, Aug 10, 2022 at 08:03:45AM +0200, Andreas Beckmann wrote:
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown 
> debugging section .debug_addr
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown 
> debugging section .debug_addr

FWIW this kind of errors can also happen with GCC with -gsplit-dwarf,
I just hit it in WebKitGTK:

   https://gcc.gnu.org/wiki/DebugFission

Berto



Bug#1008098: gcc-10: segfaults when building WebKitGTK 2.36.0

2022-03-26 Thread Alberto Garcia
On Thu, Mar 24, 2022 at 11:54:31AM +0100, Alberto Garcia wrote:
> > I'm trying to build webkit2gtk 2.36.0 for bullseye using GCC 10
> > and I get segfaults in several places.
> 
> FYI I was bisecting the problem and the culprit seems to be
> the transition from WebKit's own implementation of Variant to
> std::variant, this exact commit:
> 
>https://trac.webkit.org/changeset/283982/webkit

I also decided to try a complete webkit2gtk build with different
gcc-10 packages to see when the problems started to happen.

gcc-10 10.2.0-16 is where the first errors appear (see
below). 10.2.0-15 and all earlier versions can build webkit2gtk 2.36.0
without problems.

gcc 8 (from buster) works fine as well.

This is the error message from gcc-10 10.2.0-16

In file included from 
WebCore/DerivedSources/unified-sources/UnifiedSource-3c72abbe-57.cpp:1:
../Source/WebCore/platform/network/ResourceResponseBase.cpp: In member function 
‘void 
WebCore::ResourceResponseBase::sanitizeHTTPHeaderFieldsAccordingToTainting()’:
../Source/WebCore/platform/network/ResourceResponseBase.cpp:455:6: error: type 
precision mismatch in switch statement
  455 | void ResourceResponseBase::sanitizeHTTPHeaderFieldsAccordingToTainting()
  |  ^~~~
switch (_1) , case 0: , case 1: , case 
2: , case 3: >
../Source/WebCore/platform/network/ResourceResponseBase.cpp:455:6: internal 
compiler error: ‘verify_gimple’ failed
0x128422d verify_gimple_in_seq(gimple*)
../../src/gcc/tree-cfg.c:5144
0xf85436 gimplify_body(tree_node*, bool)
../../src/gcc/gimplify.c:14888
0xf856a3 gimplify_function_tree(tree_node*)
../../src/gcc/gimplify.c:14978
0xdbbe27 cgraph_node::analyze()
../../src/gcc/cgraphunit.c:670
0xdbee27 analyze_functions
../../src/gcc/cgraphunit.c:1227
0xdbf9f2 symbol_table::finalize_compilation_unit()
../../src/gcc/cgraphunit.c:2986

Berto



Bug#1008098: gcc-10: segfaults when building WebKitGTK 2.36.0

2022-03-24 Thread Alberto Garcia
On Tue, Mar 22, 2022 at 01:27:06PM +0100, Alberto Garcia wrote:

> I'm trying to build webkit2gtk 2.36.0 for bullseye using GCC 10 and
> I get segfaults in several places.

FYI I was bisecting the problem and the culprit seems to be
the transition from WebKit's own implementation of Variant to
std::variant, this exact commit:

   https://trac.webkit.org/changeset/283982/webkit

Berto



Bug#1008098: gcc-10: segfaults when building WebKitGTK 2.36.0

2022-03-22 Thread Alberto Garcia
Package: gcc-10
Version: 10.3.0-14
Severity: normal

Hi,

I'm trying to build webkit2gtk 2.36.0 for bullseye using GCC 10 and I
get segfaults in several places.

I tried GCC 10 from testing/sid and the problem is exactly the same.

This is the full preprocessed file:

   https://people.debian.org/~berto/UnifiedSource-3a52ce78-38.ii.xz

And this is the command line:

   /usr/bin/c++ -O2 -std=c++2a -c UnifiedSource-3a52ce78-38.ii

I'm doing all of this in a clean pbuilder chroot.

The segfault is not 100% deterministic, sometimes I have to try a
couple of times, but it is very easy to reproduce. However I cannot
reproduce it in a different computer using the same pbuilder chroot,
which suggests that the problem is related to the hardware / OS of the
first computer.

However in that same machine where I'm observing those crashes I can
build webkit using gcc 11 just fine, I actually ran a dozen of builds
and I had no problems whatsoever.

Here is the complete output of gcc, in both bullseye and testing/sid.

Using GCC 10 from bullseye:

# c++ -v
Using built-in specs.
COLLECT_GCC=c++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-10 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210110 (Debian 10.2.1-6)

# /usr/bin/c++ -O2 -std=c++2a -c UnifiedSource-3a52ce78-38.ii
In file included from ../Source/WebCore/bindings/js/JSDOMConvert.h:47,
 from ../Source/WebCore/bindings/js/JSDOMPromiseDeferred.h:29,
 from ../Source/WebCore/dom/AbortSignal.h:30,
 from ../Source/WebCore/dom/AddEventListenerOptions.h:28,
 from WebCore/DerivedSources/JSAddEventListenerOptions.h:23,
 from WebCore/DerivedSources/JSEventTarget.cpp:28,
 from 
WebCore/DerivedSources/unified-sources/UnifiedSource-3a52ce78-38.cpp:1:
../Source/WebCore/bindings/js/JSDOMConvertUnion.h: In instantiation of 'static 
WebCore::Converter >::ReturnType 
WebCore::Converter >::convert(JSC::JSGlobalObject&, 
JSC::JSValue) [with T = 
{WebCore::IDLAllowSharedAdaptor, 
WebCore::IDLAllowSharedAdaptor}; 
WebCore::Converter >::ReturnType = 
std::variant, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > >]':
../Source/WebCore/bindings/js/JSDOMConvertUnion.h:413:119:   required from here
../Source/WebCore/bindings/js/JSDOMConvertUnion.h:211:76:   in 'constexpr' 
expansion of 
'returnValue.std::optional, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > > >::value()'
/usr/include/c++/10/optional:931:28:   in 'constexpr' expansion of 
'((std::_Optional_base_impl, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > >, 
std::_Optional_base, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > >, false, false> 
>*)((std::optional, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > > 
>*)this))->std::_Optional_base_impl, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > >, 
std::_Optional_base, 
WTF::DefaultRefDerefTraits >, 
WTF::RefPtr, 
WTF::DefaultRefDerefTraits > >, false, false> 
>::_M_is_engaged()'
../Source/WebCore/bindings/js/JSDOMConvertUnion.h:377:5: internal compiler 
error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.

 --

Using GCC 10 from testing/sid

# g++-10 -v
Using built-in specs.
COLLECT_GCC=g++-10

Bug#973293: gcc-10: internal compiler error: ‘verify_gimple’ failed

2020-11-21 Thread Alberto Garcia
On Wed, Oct 28, 2020 at 12:07:03AM +0100, Alberto Garcia wrote:
> Package: gcc-10
> Version: 10.2.0-15
> Severity: important
> 
> Hi,
> 
> gcc is causing a FTBFS on the latest releases of webkit2gtk and
> wpewebkit (2.30.2-1 in both cases) on armel and armhf with the
> following error message:

We have a workaround for this in WebKit so this is not stopping the
build anymore. Feel free to lower the severity if you want.

https://trac.webkit.org/changeset/269948/webkit

Berto



Bug#973293: gcc-10: internal compiler error: ‘verify_gimple’ failed

2020-10-28 Thread Alberto Garcia
Package: gcc-10
Version: 10.2.0-15
Severity: important

Hi,

gcc is causing a FTBFS on the latest releases of webkit2gtk and
wpewebkit (2.30.2-1 in both cases) on armel and armhf with the
following error message:

../Source/WebCore/platform/network/ResourceResponseBase.cpp:440:6: internal 
compiler error: ‘verify_gimple’ failed
0xba2aa3 verify_gimple_in_seq(gimple*)
  ../../src/gcc/tree-cfg.c:5144
0x823cdf gimplify_body(tree_node*, bool)
  ../../src/gcc/gimplify.c:14888
0x8240d3 gimplify_function_tree(tree_node*)
  ../../src/gcc/gimplify.c:14978
0x5fb1eb cgraph_node::analyze()
  ../../src/gcc/cgraphunit.c:670
0x5fe7ff analyze_functions
  ../../src/gcc/cgraphunit.c:1227
0x5ff963 symbol_table::finalize_compilation_unit()
  ../../src/gcc/cgraphunit.c:2986

You can see the full log here (warning: its size is 16MB):

https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk=armel=2.30.2-1=1603462626=0

Berto


Bug#794778: Should update to gcc-5-doc packages

2016-05-27 Thread Alberto Garcia
On Thu, Aug 06, 2015 at 04:14:59PM +0200, Yuri D'Elia wrote:
> Package: gcc-doc
> Version: 5:4.9.2-1
> Severity: normal
> 
> Now that gcc 5 is the new default, gcc-doc/cpp-doc/etc should depend
> on the newer 5 versions.

Is there any technical reason why this hasn't been fixed, or just lack
of time?

Thanks!

Berto



Bug#735310: Error: bad register name `%bpl' in i386

2014-01-14 Thread Alberto Garcia
Package: gcc-4.8
Version: 4.8.2-12
Severity: important

webkitgtk 2.3.4 FTBFS with the latest gcc-4.8:

../Source/WTF/wtf/Atomics.h: Assembler messages:
../Source/WTF/wtf/Atomics.h:300: Error: bad register name `%sil'
[...]

You can see the full log here:

   
https://buildd.debian.org/status/fetch.php?pkg=webkitgtkarch=i386ver=2.3.4-1stamp=1389693794

My understanding is that gcc is incorrectly producing x86-64 registers
when generating x86 code.

I managed to narrow it down with a pre-processed version of the
CodeBlock.cpp source file from webkit (I can attach it or post it
somewhere, it's ~400KB of compressed code):

$ gcc -O1 -m32 --std=c++11 -c CodeBlock.ii 
../Source/WTF/wtf/Atomics.h: Assembler messages:
../Source/WTF/wtf/Atomics.h:300: Error: bad register name `%bpl'
../Source/WTF/wtf/Atomics.h:300: Error: bad register name `%bpl'
../Source/WTF/wtf/Atomics.h:300: Error: bad register name `%dil'

This works fine, though (which I don't quite understand since
-frename-registers should already be enabled by -O1):

$ gcc -O1 -m32 --std=c++11 -c -frename-registers CodeBlock.ii 

Here's the relevant part of the source file:

inline bool weakCompareAndSwap(uint8_t* location, uint8_t expected, uint8_t 
newValue)
{
unsigned char result;
asm volatile(
lock; cmpxchgb %3, %2\n\t
sete %1
: +a(expected), =q(result), +m(*location)
: r(newValue)
: memory
);
return result;
}

This upstream GCC bug is related:

   http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153

Although the suggestion to use '=r' instead of '=q' doesn't seem to
solve the problem.

Berto

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.8 depends on:
ii  binutils2.24-2
ii  cpp-4.8 4.8.2-12
ii  gcc-4.8-base4.8.2-12
ii  libc6   2.17-97
ii  libcloog-isl4   0.18.1-3
ii  libgcc-4.8-dev  4.8.2-12
ii  libgmp102:5.1.3+dfsg-1
ii  libisl100.12.1-2
ii  libmpc3 1.0.1-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages gcc-4.8 recommends:
ii  libc6-dev  2.17-97

Versions of packages gcc-4.8 suggests:
ii  binutils [binutils-gold]  2.24-2
ii  gcc-4.8-doc   4.8.2-2
pn  gcc-4.8-locales   none
pn  gcc-4.8-multilib  none
pn  libasan0-dbg  none
pn  libatomic1-dbgnone
pn  libbacktrace1-dbg none
pn  libgcc1-dbg   none
pn  libgomp1-dbg  none
pn  libitm1-dbg   none
pn  libquadmath0-dbg  none
pn  libtsan0-dbg  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20140114152241.11168.43801.reportbug@perseus.local



Bug#686645: (no subject)

2012-09-13 Thread Alberto Garcia
On Tue, Aug 14, 2012 at 04:36:47PM +0200, Emmanuel Kasper wrote:

 Sorry Mame still segfaults with mame -O3 and the latest gcc
 available in debian

I filed the bug upstream:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54569

Berto


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120913144817.ga16...@igalia.com