common/src/CommonKernels.cpp:
In member function ‘void OpenMM::Common
CalcGayBerneForceKernel::sortAtoms()’:
/jade/home/tru/build/openmm/openmm-8.2.0/platforms/common/src/CommonKernels.cpp:5375:6:
internal compiler error: in vect
_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509
5
Package: g++-12
Version: 12.2.0-14
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
compiling openMM relesed version 8.2.0 with cuda 12.8 support on
x86_64
* What exactly did you do (or no
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
-f
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:
https://buildd.debian.org/status/fetch.php?
pkg=pytorch&arch=arm64&ver=2.6.0%2Bdfsg-1%7Eexp1&stamp=1739418834&raw=0
This is a regression. Setting CC=gcc-13 and
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-prot
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
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
-O2 -c 1091161.cpp
during RTL pass: expand
1091161.cpp: In function 'void ccosh()':
1091161.cpp:16:56: internal compiler error: Segmentation fault
16 | complex(z_.real(), z_.imag() * copysign(1.0, ccosh_x));
|
++-15.
On some quick searches ("simplify_context::simplify_subreg", "gen_xorsigndf3")
I found no corresponding upstream bug report.
# g++-14 -O2 -c 1091161.cpp
during RTL pass: expand
1091161.cpp: In function 'void ccosh()':
1091161.cpp:16:56: internal compiler error:
Package: g++-14
Version: 14.2.0-6
Severity: normal
Dear Maintainer,
* What led up to the situation?
After converting a C++ header file to a module-defining source file the
compiler failed to compile it and reports an internal compiler error
* What exactly did you do (or not do) that was
Your message dated Fri, 30 Aug 2024 19:57:10 +0200
with message-id
and subject line Re: Bug#1073925: libstdc++-14-dev: Using multiple import
statements generates an internal compiler error
has caused the Debian Bug report #1073925,
regarding libstdc++-14-dev: Using multiple import statements
Processing control commands:
> tags -1 + moreinfo
Bug #1073925 [libstdc++-14-dev] libstdc++-14-dev: Using multiple import
statements generates an internal compiler error
Added tag(s) moreinfo.
--
1073925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073925
Debian Bug Tracking Sys
headers using compilation commands
like
g++ --std=c++23 -Wall -fmodules-ts -x c++-system-header vector
and importing those compiled system headers in a program results in an
internal compiler error when 'import ;' is also used.
* What exactly did you do (or not do) that was eff
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 #975142,
regarding internal compiler error: ‘verify_type’ failed
to be marked as done.
This means that you claim that the problem has
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 #1013122,
regarding gcc-10: internal compiler error: in move_insn
to be marked as done.
This means that you claim that the problem
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, 30 Jun 2024 14:46:00 +
with message-id
and subject line Bug#1071140: fixed in gcc-14 14.1.0-3
has caused the Debian Bug report #1071140,
regarding gcc-14: internal compiler error: in find_or_generate_expression, at
tree-ssa-pre.cc:2780 on riscv64
to be marked as done
On 30.05.24 08:40, Jiawei wrote:
> We had fixed this on gcc upstream ——
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e
please backport that upstream to the GCC 14 branch.
Backported it into releases/gcc-14 branch,
https://gcc.gnu.org/git/?p=gcc.git;a=s
importing those compiled system headers in a program results in an
internal compiler error when 'import ;' is also used.
* What exactly did you do (or not do) that was effective (or
ineffective)?
First the system headers where compiled using the abovementioned commad.
Then the compil
On 30.05.24 08:40, Jiawei wrote:
We had fixed this on gcc upstream ——
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e
please backport that upstream to the GCC 14 branch.
Hi,
On Thu, May 30, 2024 at 2:45 PM Jiawei wrote:
>
> We had fixed this on gcc upstream ——
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e
>
\o/.
Thanks for so quickly fix!
> Thanks for your report.
Okay, I will close this once I can verify this on Deb
We had fixed this on gcc upstream ——
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e
Thanks for your report.
BR,
Jiawei
> Source: gcc-14
> Version: 14-20240429-1
> Severity: important
> X-Debbugs-Cc: numbk...@gmail.com
>
> Dear Maintainer,
>
> We found a gcc internal compiler error when compile a c source code(from
> ksco):
>
>
> ```
> #include
> typedef int npy_i
Source: gcc-14
Version: 14-20240429-1
Severity: important
X-Debbugs-Cc: numbk...@gmail.com
Dear Maintainer,
We found a gcc internal compiler error when compile a c source code(from
ksco):
```
#include
typedef int npy_intp;
static inline __attribute__(()) int vaddq_f32();
static inline
Your message dated Tue, 17 Oct 2023 15:50:51 +0200
with message-id <6de51b28-6dcf-4e63-a3a4-5e22fc6ff...@debian.org>
and subject line Re: Bug#1053826: gcc-12: internal compiler error with template
specialization on floating point non-type-param in C++20 mode
has caused the Debian Bug
dbolt only gcc-trunk, not
gcc-13, compiles this, so from my point of view, it may be a Debian patch in
gcc-13 in sid, which fixes this.
The error (on gcc-12 from sid) is this:
$ g++-12 -std=c++20 -o test test.cpp
test.cpp: In function ‘int main()’:
test.cpp:13:29: internal compiler error: in unify, a
-std=c++20 -o test test.cpp
test.cpp: In function ‘int main()’:
test.cpp:13:29: internal compiler error: in unify, at cp/pt.cc:24903
13 | return F::foo();
| ^~
0x7f41729256c9 __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
Your message dated Tue, 18 Jul 2023 15:08:41 +0200
with message-id <21f622ec-c435-8fa0-ee73-8ab5bbcf4...@debian.org>
and subject line fixed
has caused the Debian Bug report #975219,
regarding elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at
tree-nested.c:288
to be mar
Your message dated Tue, 11 Jul 2023 14:32:34 +0200
with message-id <0f87cdfb-32ce-5b22-3f1f-8c49fc866...@debian.org>
and subject line Re: Bug#1040823: PR target/110560: internal compiler error: in
extract_constrain_insn_cached, at recog.cc:2704
has caused the Debian Bug report #1040823,
reg
Package: g++-13
Version: 13.1.0-7
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110560
Affects: src:highway
src:highway fails to compile on riscv64. Confirmed upstream. Already
fixed in GCC14, backported to GCC13:
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110560#c2
Your message dated Fri, 30 Jun 2023 15:49:45 +
with message-id
and subject line Bug#1038768: fixed in gcc-13 13.1.0-7
has caused the Debian Bug report #1038768,
regarding PR110280: internal compiler error: in const_unop, at
fold-const.cc:1884
to be marked as done.
This means that you claim
Your message dated Fri, 30 Jun 2023 15:49:45 +
with message-id
and subject line Bug#1038774: fixed in gcc-13 13.1.0-7
has caused the Debian Bug report #1038774,
regarding PR110264: internal compiler error:
riscv_vector::vector_insn_info::get_avl_reg_rtx
to be marked as done.
This means that
Package: g++-13
Version: 13.1.0-6
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110264
Affects: src:highway
src:highway fails to compile on riscv64. Confirmed upstream. Fixed in GCC14
Package: g++-13
Version: 13.1.0-6
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
Affects: src:highway
src:highway fails to compile on arm64. Confirmed upstream
Your message dated Sat, 20 May 2023 11:22:09 +0200
with message-id
and subject line fixed
has caused the Debian Bug report #1034554,
regarding internal compiler error: in finalize_new_accesses, at
rtl-ssa/changes.cc:471
to be marked as done.
This means that you claim that the problem has been
go/transform_test.cc:
In function 'void
hwy::N_RVV::ForeachCountAndMisalign::operator()(T, D) const
[with T = unsigned char; D = hwy::N_RVV::Simd;
Test = hwy::N_RVV::TestGenerate]':
/home/malat/highway-1.0.4~git20230317.8681eb8/hwy/contrib/algo/transform_test.cc:133:3:
internal compiler erro
Your message dated Tue, 09 Aug 2022 19:35:01 +
with message-id
and subject line Bug#1016701: fixed in gcc-12 12.1.0-8
has caused the Debian Bug report #1016701,
regarding gdc-12: internal compiler error: in add_stack_var, at cfgexpand.cc:476
to be marked as done.
This means that you claim
emu2/build/../src/base/core/int.c: In function ‘int33_unrevect_fixup’:
.../dosemu2/build/../src/base/core/int.c:1748:1: internal compiler error: in
move_insn, at haifa-sched.c:5471
1748 | }
| ^
0x7f14e033cd09 __libc_start_main
../csu/libc-start.c:308
Please submit a full bug re
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
_map.cpp.o
-MF
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o.d
-o
test/CMakeFiles/test_concurrent_unordered_map.dir/tbb/test_concurrent_unordered_map.cpp.o
-c /<>/test/tbb/test_concurrent_unordered_map.cpp
malloc(): unaligned tcache chunk detected
malloc():
Package: gcc-11
Version: 11.2.0-12
GCC 11 crashes on armel und s390x for certain
code involving VLAs. Same code builds with older
GCC:
https://buildd.debian.org/status/package.php?p=bart-view
This may also be related to a build failure on i386
for a different package:
https://salsa.debian.org/
Please work around it by using gcc-9 for bullseye. I'm not going to cherry-pick
single patches from the branch.
As said in https://lists.debian.org/debian-release/2021/03/msg00027.html
I'll provide GCC 10.3 for backports.
Processing control commands:
> reassign -1 gcc-10
Bug #986519 [src:nheko] nheko: FTBFS: internal compiler error
Bug reassigned from package 'src:nheko' to 'gcc-10'.
No longer marked as found in versions nheko/0.7.2-3.
Ignoring request to alter fixed versions of bug #98
Will a fixed version be uploaded to unstable soon? I'd like to upload a
newer version of nheko, but it won't build until a fixed gcc is
available.
Thanks
--
Hubert Chathi -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 D
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 nheko: FTBFS: internal compiler error
to be marked as done.
This means that you claim that the problem has been dealt with
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 nheko: FTBFS: internal compiler error
to be marked as done.
This means that you claim that the problem has been dealt with
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 mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
to be
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 mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
to be
Processing control commands:
> reassign -1 src:gcc-10 10.2.1-6
Bug #980596 [src:mkvtoolnix] mkvtoolnix: FTBFS:
src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error:
Segmentation fault
Bug reassigned from package 'src:mkvtoolnix' to 'src:gcc-10'.
No
Processing commands for cont...@bugs.debian.org:
> reassign 980629 gcc-10 10.2.1-6
Bug #980629 [src:nheko] nheko: FTBFS: internal compiler error
Bug reassigned from package 'src:nheko' to 'gcc-10'.
No longer marked as found in versions nheko/0.7.2-3.
Ignoring request to
Your message dated Sat, 9 Jan 2021 16:46:08 +0100
with message-id <77a2ab63-e5d1-2997-c93d-9268fb7d3...@debian.org>
and subject line fixed
has caused the Debian Bug report #973293,
regarding gcc-10: internal compiler error: ‘verify_gimple’ failed
to be marked as done.
This means that you
Package: g++-10
Version: 10.2.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
There is not possible to compile any even simple program. Every time g++
produces following errors:
cc1plus: internal compiler error: in cpp_diagnostic_at, at libcpp/errors.c:41
0x5cb277
I got some input from compiler gurus.
It seems that the corresponding upstream bug is:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52830
(And this may be the same issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91590 )
Alex Coplan has added a reduced testcase to 52380 derived from the
polyma
* Lucas Nussbaum:
> Hi Michael,
>
> On 22/11/20 at 15:32 +0100, Michael Banck wrote:
>> Hi Lucas,
>>
>> That looks like an ICE, shouldn't that be filed with gfortran?
>
> Usually my logic is: if there's only one similar failure, I file a bug
> against the affected package, rather than against the
Hi Michael,
On 22/11/20 at 15:32 +0100, Michael Banck wrote:
> Hi Lucas,
>
> That looks like an ICE, shouldn't that be filed with gfortran?
Usually my logic is: if there's only one similar failure, I file a bug
against the affected package, rather than against the toolchain package
or the librar
smatch
> > `dpkg-buildflags --get LDFLAGS` -c exxengy.f90
> > exxengy.f90:6:18:
> >
> > 6 | subroutine exxengy
> > | ^
> > internal compiler error: in lookup_field_for_decl, at tree-nested.c:288
> > 0x71106d lookup_field_for
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
So this is the failing command from the build:
g++ -c -o
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MMD -MT
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MF
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/Spar
COMPILER_USED=10.2.0'
fails quickly with the same
/home/wookey/debian/polymake-4.1/include/core/polymake/GenericVector.h:304:11:
internal compiler error: canonical types differ for identical types error.
This only gets to about 500MB RAM usage before dying.
So, no this doesn't seem to
Processing control commands:
> block 974058 by -1
Bug #974058 [src:polymake] polymake: FTBFS on arm64: internal compiler error:
canonical types differ for identical types
974058 was not blocked by any bugs.
974058 was blocking: 968912
Added blocking bug(s) of 974058: 974073
--
974058: ht
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
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
Fixed in version 10.2.0-12
$ cat test.c
int main() {
return 0;
}
$ gcc --version
gcc (Debian 10.2.0-12) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PAR
$ gcc --version
gcc (Debian 10.2.0-11) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc --target-help
gcc: internal compiler error
reproducible here.
what other info do you need?
Processing control commands:
> tags -1 + moreinfo
Bug #971365 [gcc-10] gcc: internal compiler error: Segmentation fault signal
terminated program cc1
Added tag(s) moreinfo.
--
971365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971365
Debian Bug Tracking System
Contact
>* What led up to the situation?
>
> $ cat test.c
>
> int main() {
> return 0;
> }
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> $ gcc test.c
>
> gcc: internal compiler error: Segmentation fault si
(or not do) that was effective (or
ineffective)?
$ gcc test.c
gcc: internal compiler error: Segmentation fault signal terminated program cc1
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
* What was the outcome of this action?
$ gcc
Processing commands for cont...@bugs.debian.org:
> reassign 959613 g++-9
Bug #959613 [src:range-v3] range-v3: FTBFS: unique.cpp:58:10: internal compiler
error: in dependent_type_p, at cp/pt.c:25610
Bug reassigned from package 'src:range-v3' to 'g++-9'.
No longer marked as
We worked around this by removing the use of `goto` within the OpenMP
loop:
https://github.com/soedinglab/MMseqs2/pull/309/commits/a5b2f230bb6fb3ab79bed626d2f89d59e1a5b2df
However, a non-crash error message would be appreciated.
On Tue, 19 May 2020 12:38:57 +0200 "Michael R. Crusoe"
wrote:
> Attached is the reduced example.
Pardon me, that first attachment only fails on gcc-snapshot's g++
Attached is an example that does fail on g++-9, g++-10, and
gcc-snapshot's g++
class a {
public:
long b();
};
class c {
public:
function '_Z1sv._omp_fn.0':
clusthash_prep.cpp:41:9: internal compiler error: in asan_expand_mark_ifn, at
asan.c:3194
41 | #pragma omp parallel
| ^~~
0x149b9425ce0a __libc_start_main
../csu/libc-start.c:308
Attached is the reduced example.
-- System Informati
While this has been re-assigned to gcc as a compiler regression, let
me just mention for the HepMC3 maintainers, that there is a workaround
from the authors which makes HepMC3 compile again:
https://gitlab.cern.ch/hepmc/HepMC3/-/commit/ba38f14d8f56c16cc4105d98f6d4540c928c6150
(That patch is fo
Processing control commands:
> reassign -1 gcc-9 9.2.1-28
Bug #952628 [src:hepmc3] hepmc3: FTBFS: Feature.h:296:69: internal compiler
error: in get_fns, at cp/tree.c:2455
Bug reassigned from package 'src:hepmc3' to 'gcc-9'.
No longer marked as found in versions hepmc3/3.
Processing control commands:
> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93299
Bug #949024 [g++-9] g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14
Set Bug forwarded-to-address to
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93299'.
--
949024: https://bugs.debian.org/cgi-bi
creduce output (and yes, this isn't a valid program, but it still
shouldn't ICE):
template struct a {
enum { b };
};
class c;
template class __attribute__((aligned((a::b d {};
class : d<0> {
Control: tags -1 + moreinfo
On 16.01.20 23:34, Rebecca N. Palmer wrote:
> Control: retitle -1 g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14 or
> higher
>
> This also happens with LLVM 9 (which makes sense given that the error message
> points to code in beignet itself):
>
>
Processing control commands:
> tags -1 + moreinfo
Bug #949024 [g++-9] g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14
Added tag(s) moreinfo.
--
949024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> retitle -1 g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14
Bug #949024 [g++-9] g++: internal compiler error on beignet + llvm10
Changed Bug title to 'g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14'
from 'g++: internal compiler error o
Control: retitle -1 g++: ICE at cp/pt.c:15779 on beignet in -std=gnu++14
or higher
This also happens with LLVM 9 (which makes sense given that the error
message points to code in beignet itself):
LLVM 9LLVM 10
-std=c++0x successstd::index_sequence fail
-std
Package: g++-9
Version: 9.2.1-23
Control: affects -1 src:beignet
Trying to build beignet with llvm 10 and the default -std fails with
this internal compiler error. (See attached for exact changes; it
previously used -std=c++0x, but that fails with LLVM 10 because it can't
fin
Processing control commands:
> affects -1 src:beignet
Bug #949024 [g++-9] g++: internal compiler error on beignet + llvm10
Added indication that 949024 affects src:beignet
--
949024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949024
Debian Bug Tracking System
Contact
Your message dated Thu, 07 Feb 2019 03:13:19 +
with message-id
and subject line Bug#920171: Removed package(s) from unstable
has caused the Debian Bug report #845493,
regarding g++-6: Internal compiler error in tsubst, at cp/pt.c:13073
to be marked as done.
This means that you claim that the
Package: gcc-6
Version: 6.3.0-18+deb9u1
Severity: minor
Dear Maintainer,
* What led up to the situation?
While writing SIMD code, gcc gave me the following error message:
cc-error.c: In function ‘f.avx512f.0’:
cc-error.c:3:1: internal compiler error: in expand_debug_locations, at
Your message dated Fri, 21 Sep 2018 11:12:00 +0200
with message-id
and subject line fixed in 6.4.0-20
has caused the Debian Bug report #902293,
regarding gcc-6: internal compiler error in convert_move on arm
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: severity -1 important
On 24.06.2018 17:56, Michael Gilbert wrote:
package: src:gcc-6
version: 6.4.0-18
severity: grave
control: affects -1 src:chromium-browser
forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86166
This was marked as a duplicate upstream and closed, but it seems
Processing control commands:
> severity -1 important
Bug #902293 [src:gcc-6] gcc-6: internal compiler error in convert_move on arm
Severity set to 'important' from 'grave'
--
902293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902293
Debian Bug Tra
Processing control commands:
> severity -1 important
Bug #902293 [src:gcc-6] gcc-6: internal compiler error in convert_move on arm
Ignoring request to change severity of Bug 902293 to the same value.
--
902293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902293
Debian Bug Tracking Sys
package: src:gcc-6
version: 6.4.0-18
severity: grave
control: affects -1 src:chromium-browser
forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86166
This was marked as a duplicate upstream and closed, but it seems like
it should be considered a separate issue.
The latest chromium upload no
Processing control commands:
> affects -1 src:chromium-browser
Bug #902293 [src:gcc-6] gcc-6: internal compiler error in convert_move on arm
Added indication that 902293 affects src:chromium-browser
--
902293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902293
Debian Bug Tracking Sys
Package: gfortran
Version: 4:7.3.0-3
Severity: important
Tags: upstream
While compiling any of the recent versions of exciting: exciting-code.org
gfortran aborts. If I comment the portions of code implied in the error message,
it aborts at other points.
The first position where it aborts is at the
1 - 100 of 725 matches
Mail list logo
