Your message dated Fri, 28 Mar 2025 16:54:01 +0100
with message-id
and subject line Bug #1101322 is a duplicated of #980429 (closed)
has caused the Debian Bug report #1101322,
regarding g++-10: g++ randomly segfaults on clang code on Debian 11
to be marked as done.
This means that you claim that
Package: g++-10
Version: 10.2.1-6
Severity: normal
X-Debbugs-Cc: yoann.con...@smile.fr
Dear Maintainer,
* What led up to the situation?
I was trying to build clang for the Yocto project and it failed
randomly (See [0] for the bug reported on the Yocto project)
The file triggering the crash is
Dear Maintainer / Matthias Klose,
As with bug report 1094919: after upgrading g++ to g++-15 the code for
which I filed a bug-report on Sat, 01 Feb 2025 11:08:23 +0100 compiles
flawlessly when using g++-15.
Since the issue I reported in bug report 1094907 has disappeared I'd like to
clos
Dear Maintainer / Matthias Klose,
Following the suggestion I received from Matthias (Wed, 12 Feb 2025 11:06:02
+0100) I just installed g++-15 from experimental ((Debian 15-20250213-1)
15.0.1 20250213), and reran the code for which I filed a bug-report on Sat,
01 Feb 2025 14:16:05 +0100.
With g
On 2/14/25 15:17, Matthias Klose wrote:
Control: tags -1 + moreinfo
On 13.02.25 21:41, Mo Zhou wrote:
Control: reopen -1
The problem persists, and the buildd is still failing on it several
hours ago:
still unable to reproduce with
g++ -c -std=gnu++17 -g -gsplit-dwarf -O3 -fopenmp -fPIC
ng CC=gcc-13 and CXX=g++-13 in d/rules can avoid
this issue. The problem persists with GCC-15 in experimental.
ok, pytorch 2.6.0.
the build log says:
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug
Processing control commands:
> tags -1 + moreinfo
Bug #1094828 [g++-14] g++ internal compiler error on arm64 when compiling
pytorch
Ignoring request to alter tags of bug #1094828 to the same tags previously set
--
1094828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094828
Debian
Control: tags -1 + moreinfo
On 13.02.25 21:41, Mo Zhou wrote:
Control: reopen -1
The problem persists, and the buildd is still failing on it several
hours ago:
still unable to reproduce with
g++ -c -std=gnu++17 -g -gsplit-dwarf -O3 -fopenmp -fPIC
-fstack-protector-strong -fstack-clash
Processing control commands:
> reopen -1
Bug #1094828 {Done: Matthias Klose } [g++-14] g++ internal
compiler error on arm64 when compiling pytorch
Bug reopened
Ignoring request to alter fixed versions of bug #1094828 to the same values
previously set
--
1094828: https://bugs.debian.org/
Your message dated Wed, 12 Feb 2025 20:51:43 +0100
with message-id
and subject line unable to reproduce, closing
has caused the Debian Bug report #1094828,
regarding g++ internal compiler error on arm64 when compiling pytorch
to be marked as done.
This means that you claim that the problem has
Package: g++-14
Version: 14.2.0-12
Severity: normal
Dear Maintainer,
* What led up to the situation?
When working on the conversion of existing projectss to projects using modules
the compiler reported an (unclear) error message when compiling a source file
defining a module.
* What
Package: gcc-bpf
Version: 14.2.0-1+1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
i noticed that as soon as i enable the -g option to bpf-gcc the builds are non-
deterministic.
* What
Control: tags -1 + moreinfo
On 31.01.25 15:46, M. Zhou wrote:
Package: g++-14
Version: 14.2.0-14
Severity: important
Dear maintainer,
We noted that pytorch 2.6.0 FTBFS on arm64 due to an internal compiler
error from g++. The relevant part of error log reads:
```
Please submit a full bug
Processing control commands:
> tags -1 + moreinfo
Bug #1094828 [g++-14] g++ internal compiler error on arm64 when compiling
pytorch
Added tag(s) moreinfo.
--
1094828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094828
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Package: g++-14
Version: 14.2.0-14
Severity: important
Dear maintainer,
We noted that pytorch 2.6.0 FTBFS on arm64 due to an internal compiler
error from g++. The relevant part of error log reads:
```
/usr/bin/c++ -DAT_BUILD_ARM_VEC256_WITH_SLEEF -DAT_PER_OPERATOR_HEADERS
-DBUILD_ONEDNN_GRAPH
Your message dated Mon, 27 Jan 2025 13:21:01 +
with message-id
and subject line Bug#1091161: fixed in gcc-14 14.2.0-15
has caused the Debian Bug report #1091161,
regarding g++14/g++-15 arm64 regression: ICE in
simplify_context::simplify_subreg()
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> reassign 1091161 g++-14 14.2.0-12
Bug #1091161 [src:libthrust] libthrust: FTBFS on arm64: ccosh.h:102:60:
internal compiler error: Segmentation fault
Bug reassigned from package 'src:libthrust' to 'g++-14'.
No longer mark
Package: g++-14
Version: 14.2.0-8
Severity: normal
Dear Maintainer,
* What led up to the situation?
When constructing a module file changing the order of importing system header
files may result in a compilation failure.
* What exactly did you do (or not do) that was effective (or
Package: g++-14
Version: 14.2.0-8
Severity: normal
1) Consider a program with a known-at-compile length structure of
length strictly less than 16, e.g. an array.
2) Call std::sort on it in a way that, at execution time, ensures the
arguments are within the bounds of the structure, but so
Package: g++-14
Version: 14.2.0-3
Severity: normal
Dear Maintainer,
* What led up to the situation?
When trying to import a module in a C++ source file when --std=c++23 was
specified when the module was compiled and --std=c++26 is specified when the
source file is compiled the compiler shows
Processing control commands:
> found -1 14.2.0-2
Bug #1077657 [g++-14-arm-linux-gnueabihf] g++-14-arm-linux-gnueabihf: Forward
declaration of std::vector does not compile with -O
Marked as found in versions gcc-14/14.2.0-2.
--
1077657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077
Control: found -1 14.2.0-2
Package: g++-14-arm-linux-gnueabihf
Version: 14.1.0-5
Severity: important
Dear Maintainer,
I have the following minimal program that does not compile on armhf with
-O. It however *does* compile without the optimization flag, or with or
without -O on amd64 and other architectures. (I&#
Your message dated Sun, 28 Jul 2024 15:35:35 +
with message-id
and subject line Bug#1076503: Removed package(s) from unstable
has caused the Debian Bug report #976024,
regarding g++-10 crashes for bitpacked enum class
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 28 Jul 2024 15:35:35 +
with message-id
and subject line Bug#1076503: Removed package(s) from unstable
has caused the Debian Bug report #977638,
regarding g++-10:s390x: Large classes of std::bitset and std::vector hash
the same
to be marked as done.
This means that
Your message dated Sun, 28 Jul 2024 15:35:35 +
with message-id
and subject line Bug#1076503: Removed package(s) from unstable
has caused the Debian Bug report #973698,
regarding g++-10: regresson in 10.2.0-16: internal compiler error: in
tsubst_decl, at cp/pt.c:14666
to be marked as done
Your message dated Sun, 28 Jul 2024 15:35:35 +
with message-id
and subject line Bug#1076503: Removed package(s) from unstable
has caused the Debian Bug report #1069559,
regarding g++-10: std::regex_constants::multiline (C++17) missing in
-std=gnu++20
to be marked as done.
This means that
Your message dated Sun, 28 Jul 2024 15:27:28 +
with message-id
and subject line Bug#1076502: Removed package(s) from unstable
has caused the Debian Bug report #961011,
regarding g++-9: internal compiler error: in asan_expand_mark_ifn, at
asan.c:3194
to be marked as done.
This means that you
Your message dated Sun, 28 Jul 2024 15:27:28 +
with message-id
and subject line Bug#1076502: Removed package(s) from unstable
has caused the Debian Bug report #947751,
regarding gcc/g++: fails to build ceph on armel/armhf/mipsel
to be marked as done.
This means that you claim that the
Your message dated Sun, 28 Jul 2024 15:27:28 +
with message-id
and subject line Bug#1076502: Removed package(s) from unstable
has caused the Debian Bug report #939655,
regarding g++ v9 with OpenMP segfaults with shared vectors
to be marked as done.
This means that you claim that the problem
Hi,
I could reproduce the problem with GCC 12 on aarch64, but not with GCC
13 and 14.
Using the following test program:
#include
float test(_Float16 x){
return x;
}
int main() {
printf("%f\n", test(1.0));
}
This is the error message you get on aarch64 w
Processing commands for cont...@bugs.debian.org:
> reassign 1076160 g++-12
Bug #1076160 [g++] g++: _Float16 does not work in G++ (works in GCC) on aarch64
Bug reassigned from package 'g++' to 'g++-12'.
No longer marked as found in versions gcc-defaults/1.203.
Ignoring
Package: g++
Version: 4:12.2.0-3
Severity: important
Tags: newcomer upstream
X-Debbugs-Cc: allsmiles94...@gmail.com, mikegreen10...@gmail.com
I'm looking to use 16b IEEE floating point on ARM Linux which is supported by
my target, and successfully compiles with GCC. Alas, the same file fai
Package: g++-12
Version: 12.2.0-14
Severity: important
X-Debbugs-Cc: userreen10...@gmail.com, mikegreen10...@gmail.com
-- System Information:
Debian Release: 12.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'sta
Your message dated Tue, 07 May 2024 18:59:25 +
with message-id
and subject line Bug#1026175: Removed package(s) from unstable
has caused the Debian Bug report #978511,
regarding gcc-python-plugin: non-standard gcc/g++ used for build (gcc-9)
to be marked as done.
This means that you claim
Package: g++-10
Version: 10.2.1-6
Severity: important
X-Debbugs-Cc: um4...@mutluit.com
Dear Maintainer,
the value std::regex_constants::multiline is supposed to be present
in C++17 and later (cf. for example
https://en.cppreference.com/w/cpp/regex/basic_regex/constants ),
but actually it&#
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12567
Andrew Pinski changed:
What|Removed |Added
Alias|cwg253 |
--
You are receiving this mail because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12567
Andrew Pinski changed:
What|Removed |Added
Alias||cwg253
--
You are receiving this mail b
Your message dated Tue, 30 Jan 2024 07:49:12 +
with message-id
and subject line Bug#1061670: fixed in gcc-14 14-20240130-1
has caused the Debian Bug report #1061670,
regarding gcc-14: long package description of {cpp,g++}-14-for-{build,host} has
literal arch_gnu
to be marked as done.
This
Package: gcc-14
Severity: minor
X-Debbugs-Cc: dfo...@gmail.com
Dear maintainers,
the long package description of
cpp-14-for-build cpp-14-for-host g++-14-for-build g++-14-for-host
contains the string "arch_gnu" instead of "the build" or "the host".
Eg:
...t
Package: g++-13
Severity: wishlist
X-Debbugs-Cc: olafvds...@gmail.com
Dear Maintainer,
Would it be possible to provide GCC 13 for Bookworm, perhaps via backports?
Olaf
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (50
Package: g++-12
Version: 12.2.0-14
Severity: normal
Tags: upstream
X-Debbugs-Cc: david.turner+...@raspberrypi.com
Dear Maintainer,
The attached C++ file fails to compile in GCC 12.2 using the command
`g++ --std=c++17 -c 1862683_reproducer.cpp`, but works correctly with 12.3 and
with clang
Please stop filing duplicating bogus reports. You make unproven claims
without giving any rationale.
On 14.11.23 00:04, jahway-bug-reports wrote:
Hi Matthias,
There is software which will not build natively on Debian 10/11/12 without the
gcc-multilib & g++-multilib packages
h
Your message dated Thu, 2 Nov 2023 12:50:17 +0100
with message-id <57934e79-fd66-4e21-9f12-16474c552...@klose.in-berlin.de>
and subject line Re: Bug#1055200: g++-multilib: bullseye & bookworm currently
has amd64 support for this package, add support for aarch64 (64-bit ARM)
has caused
Subject: g++-multilib: bullseye & bookworm currently has amd64 support for this
package, add support for aarch64 (64-bit ARM)
Package: g++-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Requiring the ability to com
: https://salsa.debian.org/lumag/gcc-doc
Section : non-free/doc
The source builds the following binary packages:
gcc-13-doc - documentation for the GNU compilers (gcc, gobjc, g++)
cpp-13-doc - documentation for the GNU C preprocessor (cpp)
gfortran-13-doc - documentation for the G
Your message dated Tue, 11 Jul 2023 10:21:35 +0200
with message-id
and subject line Re: g++-12-i686-linux-gnu: Install of g++-12-i686-linux-gnu
(12.1.0-7cross1) causes removal of libc6-dev:i386 (2.34-3)
has caused the Debian Bug report #1017090,
regarding g++-12-i686-linux-gnu: Install of g++-12
closing, see https://bugs.debian.org/872891
Processing control commands:
> tags -1 + moreinfo
Bug #1038134 [g++-12] g++-12: Conditional compilation error in optimized mode
Added tag(s) moreinfo.
--
1038134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
please recheck with the gcc-12 and gcc-13 packages from unstable. Also please
try to check with a standalone test case.
Package: g++-12
Version: 12.2.0-14
Severity: normal
X-Debbugs-Cc: iv...@isle.spb.ru
Dear Maintainer,
When I compile c++ code which has an error (method invoked on
null class pointer) the following problem occurs: the actual
call does not crash, since 'this' pointer is not really used
Your message dated Mon, 1 May 2023 09:45:44 +0200
with message-id <2ba70533-30e5-f901-7922-4d069cf62...@debian.org>
and subject line closing, invalid
has caused the Debian Bug report #1033145,
regarding g++-multilib: make it available on arm64 architecture (known as
aarch64)
to be marked a
Your message dated Mon, 3 Apr 2023 18:06:00 +0200
with message-id
and subject line Problem vanished.
has caused the Debian Bug report #1010519,
regarding g++-12: compilation fails on riscv64 because of always_inline when
using fmtlib
to be marked as done.
This means that you claim that the
Subject: g++-multilib: make it available on arm64 architecture (known as
aarch64)
Package: g++-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Unable to compile certain
* software without g++-multilib library
Your message dated Fri, 6 Jan 2023 16:15:09 +0100
with message-id <21464238-c04b-25f7-f5e8-e35c101e4...@ubuntu.com>
and subject line fixed in glibc
has caused the Debian Bug report #1026206,
regarding g++-13: fails to compile #include due to __float128 vs
fixincludes
to be marked as done.
On Fri, 16 Dec 2022 11:06:37 +0100 Helmut Grohne wrote:
> Package: g++-13
> Version: 13-20221214-1
> Severity: serious
>
> Hi Matthias,
>
> thanks for pushing gcc-13 into experimental already. That leaves plenty
> of time to work on it. I've located a quite fundamen
Package: g++-13
Version: 13-20221214-1
Severity: serious
Hi Matthias,
thanks for pushing gcc-13 into experimental already. That leaves plenty
of time to work on it. I've located a quite fundamental problem with it
already:
$ cat test.c++
#include
$ g++-13 -c test.c++
In file included from
Package: g++-12-i686-linux-gnu
Version: 12.1.0-7cross1
Severity: important
X-Debbugs-Cc: witold.bary...@gmail.com
For few days now (maybe a week):
On sid.
$ apt install g++-12-i686-linux-gnu
The following additional packages will be installed:
libc6-dev-i386-cross (2.33-1cross1)
libstdc
Package: g++-12
Version: 12-20220428-1
Severity: important
Dear Maintainer,
I have uploaded my package opm-common to experimental. Buildd shows that
compilation fails on riscv64 with the message:
In file included from /usr/include/fmt/format.h:48,
from
/<>/src/opm/input/e
e+friend): "
<< X::check_is_map::value
<< std::endl;
std::cerr << "** By proxy template" << std::endl;
std::cerr << "X::Proxy::VALUE (public): "
<< X::check_is_map2::value
Package: g++-11
Version: 11.2.0-19
Severity: normal
Contrary to clang++, g++ does not honor "friend" statement when evaluating
template specialization
Here is a short example:
$ cat toto6.cpp
#include
struct X {
template struct check_is_map {
static constexpr bool val
Processing control commands:
> reassign -1 src:onetbb
Bug #1005733 [g++-11] g++-11 internal compiler error when building onetbb on
riscv64
Bug reassigned from package 'g++-11' to 'src:onetbb'.
No longer marked as found in versions gcc-11/11.2.0-16.
Ignoring request to alte
Control: reassign -1 src:onetbb
Control: retitle -1 onetbb ftbfs on riscv64
this isn't reproducible at the moment. The build now fails with:
In file included from /<>/src/tbb/tools_api/ittnotify_static.c:17,
from /<>/src/tbb/itt_notify.cpp:43:
/<>/src/tbb/tools_api/ittnotify_c
Package: g++-11
Version: 11.2.0-16
Severity: normal
Justification: not release architecture, lowering severity from important
https://buildd.debian.org/status/fetch.php?pkg=onetbb&arch=riscv64&ver=2021.5.0-5&stamp=1644817169&raw=0
excerpt:
[55/315] /usr/bin/c++ -I/<>/
Package: g++-11
Version: 11.2.0-13
Severity: normal
X-Debbugs-Cc: rody...@riseup.net
Dear Maintainer,
% cat cc.cc
// For some combinations of
// - the type of inner::a
// - the array size of inner::a
// - the size of the std::array in main
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12567
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--
You are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12567
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12567
Andrew Pinski changed:
What|Removed |Added
Status|SUSPENDED |NEW
--- Comment #4 from Andrew Pinski -
Package: g++-11
Version: 11.2.0-4
Severity: normal
Dear Maintainer,
* What led up to the situation?
While performing some tests using modules I first defined a module defining a
class type. Its compilation completed flawlessly. Next I defined a module
partition defining a class type. It&#
Package: g++-11
Version: 11.2.0-4
Severity: normal
Dear Maintainer,
* What led up to the situation?
When defining a simple module in which a std::string is exported the program
compiles correctly but segfaults when it's run. When (instead of a
std::string) objects like std::vector o
Your message dated Wed, 14 Jul 2021 09:06:39 +0200
with message-id <1b3eb729-40b0-7550-61ce-c08a6a5dc...@debian.org>
and subject line Re: g++-11 internal error and fails to precompile a concept
has caused the Debian Bug report #985214,
regarding g++-11 internal error and fails to precom
Dear Matthias Klose, you wrote:
>
> (2) now shows a proper error, as shown below.
>
> Please could you report the other issues upstream?
OK.
--
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
(2) now shows a proper error, as shown below.
Please could you report the other issues upstream?
foo.cc: In substitution of ‘template requires
OstreamInsertable void operator<<(CSVTabIns&&, con
st Type&) [with Type = FMT]’:
foo.cc:11:13: required by substitution of ‘template requires
Ostream
Processing control commands:
> tags -1 + moreinfo
Bug #984670 [g++-10] g++-10: ICE in std::bind
Added tag(s) moreinfo.
--
984670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
I'm unable to reproduce this with
$ g++ -c -O3 -g -msse2 -mfpmath=sse -ftree-slp-vectorize -std=gnu++17
NasalWidget.ii
please could you recheck with gcc-10 and gcc-11 from experimental? Please also
attach the preprocessed source generated with GCC 11.
Package: g++-11
Version: 11-20210306-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Following the installation of g++-11 a previously precompilable header file
can't be precompiled anymore, and in some cases the compiler reports an
internal error requesting to sub
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #982425,
regarding g++-8: aarch64 -ftree-vectorize generates wrong code
to be marked as done.
This means that you claim that the
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #941911,
regarding g++: Broken -x/suffix handling leads to spurious -Wc++-compat warnings
to be marked as done.
This means that you
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #929966,
regarding g++-8: ICE (SIGILL in collect2) building musescore-snapshot on riscv64
to be marked as done.
This means that you
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #919577,
regarding g++-8: Can't build GN tool due to bug in raw-string parsing
to be marked as done.
This means that you claim
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #911599,
regarding g++-8: removal of old abi mangling breaks compatibility with stretch
to be marked as done.
This means that you
Your message dated Sat, 13 Feb 2021 13:07:12 +
with message-id
and subject line Bug#954831: Removed package(s) from unstable
has caused the Debian Bug report #913802,
regarding g++-8: compilation crashing on lambda capturing aliased VLA
to be marked as done.
This means that you claim that
Package: g++-8
Version: 8.4.0-7
Severity: important
Tags: patch upstream
g++-8 generates incorrect code on arm64 for -O3 if
targetting aarch64 unless tree vectorisation is disabled. This is
quite bad and affects real packages like vlc and apache arrow.
The upstream bug is https://gcc.gnu.org
Your message dated Tue, 2 Feb 2021 08:21:00 +0100
with message-id <3ae6a75a-3aed-bf46-34b1-33819ea81...@debian.org>
and subject line Fixed
has caused the Debian Bug report #949024,
regarding g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14
to be marked as done.
This means that you clai
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980596: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980596,
regarding g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
to be marked as done
Your message dated Sun, 31 Jan 2021 13:18:49 +
with message-id
and subject line Bug#980429: fixed in gcc-10 10.2.1-16
has caused the Debian Bug report #980429,
regarding g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
to be marked as done
Package: g++-10
Version: 10.2.1-6
Severity: serious
Hi,
while rebuilding src:nheko I noticed an ICE with SEGFAULT.
I've somewhat minimized the testcase with delta (from 3.3 MB to 15 KB).
Build the attached code with
x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c g
The described compiler bug is reproducible on gentoo [0] (gcc-10.2.0-r5, that is patchlevel 6).
So it is not a debian - specific bug
[0] https://github.com/Return-To-The-Roots/s25client/issues/1327#issuecomment-755180727
that is already fixed
Package: gcc-python-plugin
Severity: important
Tags: sid bullseye
User: debian-gcc@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy
This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with
Source: gcc-11
Version: 11-20201222-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Building cross compilers from gcc-11 presently fails, because it fails
moving g++-mapper-server, which is expected in .../gcc-cross/... but is
installed into .../gcc/ It seems like cross-install
Package: g++-10
Version: 10.2.1-1
Severity: normal
On s390x, std::hash returns identical values for large classes of
std::bitset and std::vector:
$ cat bug.cc
#include
#include
#include
#include
int main() {
std::bitset<2> a("00"), b("01&q
Also happens with gcc-snapshot, so this is definitely an upstream bug.
g++ (Debian 20201127-1) 11.0.0 20201127 (experimental) [master revision
3493b0c3281:5c47353bc97:5e9f814d754be790aec5b69a95699a8af2654058]
Reported upstream as: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98043
Looks like a
Package: g++-10
Version: 10.2.0-16
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
Compiling the following code crashes g++-10:
// g++-10 -std=c++2a -o /tmp/example.cpp.o -c example.cpp
enum class MyEnumClass { A };
struct MyClass
Thanks for making the issue upstream with the minimal example!
I just built with gcc-snapshot 1:20201023-1 and now I get a build error:
https://github.com/seqan/seqan3/issues/2236#issuecomment-723232918
On Fri, 6 Nov 2020 at 17:13, Matthias Klose wrote:
> Control: forwarded -1 https://gcc.gnu.
Processing control commands:
> forwarded -1 https://gcc.gnu.org/PR97745
Bug #973698 [g++-10] g++-10: regresson in 10.2.0-16: internal compiler error:
in tsubst_decl, at cp/pt.c:14666
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR97745'.
--
973698: https://bugs.debia
Control: forwarded -1 https://gcc.gnu.org/PR97745
please could you try to build the package with gcc-snapshot to see if you get an
error?
Package: g++-10
Version: 10.2.0-16
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
g++-10 10.2.0-16 causes the seqan3 3.0.2+ds-3 package to FTBFS due to a
g++ internal compiler error, which does not occur with g++-10 10.2.0-15
Details including a build log and processed
Your message dated Wed, 15 Jul 2020 20:53:55 +0300
with message-id <20200715175355.GA10447@localhost>
and subject line Re: Bug#962853: [armhf] g++: Mis-compiles code using -O1 or
higher
has caused the Debian Bug report #962853,
regarding [armhf] g++: Mis-compiles code using -O1 or higher
Package: g++-9
Version: 9.3.0-13
Severity: important
Tags: upstream
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95676
Control: affects -1 src:msgpack-c
msgpack-c's latest upload is failing a test on armhf:
--8<--
TEST(object_with_zone, system_clock_impl_min)
{
std
1 - 100 of 2017 matches
Mail list logo
