o -MF
CMakeFiles/hsail.dir/HSAILExtManager.cpp.o.d -o
CMakeFiles/hsail.dir/HSAILExtManager.cpp.o -c
"/<>/libHSAIL/HSAILExtManager.cpp"
[ 60%] Building CXX object libHSAIL/CMakeFiles/hsail.dir/HSAILInstProps.cpp.o
cd "/<>/obj-x86_64-linux-gnu/libHSAIL" &&a
Your message dated Thu, 27 Mar 2025 19:42:08 +0100
with message-id
and subject line bug report should never been filed. libxml2 is now fixed
has caused the Debian Bug report #1101231,
regarding libabigail: FTBFS: /usr/include/unicode/localpointer.h:561:26: error:
parameter declared 'auto&#
-I/<>/build/../include -I/<>/build/include
-I/<>/build -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf
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 Fri, Feb 14, 2025 at 02:20:50PM +0100, Erez wrote:
> My real question is why do we have gcc-14-aarch64-linux-gnu:arm64 in the
> pool?
It's the native compiler used for natively building arm64 packages.
Without it, we cannot build any packages on arm64.
> Cross compilers using the same host and
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
Hi Matthias,
On Fri, Feb 14, 2025 at 04:26:02PM +0100, Matthias Klose wrote:
> I don't want to apply this patch for trixie. Having these as and ld
> symlinks in the gcc_lib_dir had other issues. The main reason for that
Fair enough. However, we need some mechanism to redirect gcc into using
the
On 14.02.25 10:52, Helmut Grohne wrote:
Control: retitle -1 gcc-VER-TRIPLET may use binutils for a different
architecture
Control: severity -1 important
Control: tags -1 = confirmed patch
On Thu, Oct 03, 2024 at 12:40:53PM +0200, Erez wrote:
Just update my trixie container.
builder@5ba2a4b665
Yes, you are right.
Removing gcc-14-aarch64-linux-gnu:arm64 does solve the problem.
It was installed by dependencies.
I am using multiple architectures for cross compilation.
My real question is why do we have gcc-14-aarch64-linux-gnu:arm64 in the
pool?
Cross compilers using the same host and tar
Control: retitle -1 gcc-VER-TRIPLET may use binutils for a different
architecture
Control: severity -1 important
Control: tags -1 = confirmed patch
On Thu, Oct 03, 2024 at 12:40:53PM +0200, Erez wrote:
> Just update my trixie container.
>
> builder@5ba2a4b665d9:~$ cat /etc/debian_version
> trixi
Processing control commands:
> retitle -1 gcc-VER-TRIPLET may use binutils for a different architecture
Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross
compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"
Changed
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:
Processing control commands:
> clone -1 -2 -3
Bug #1088262 [src:python-apt] python-apt: ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so:
undefined symbol:
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm
Bug 1088262 cloned as bugs 1088
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
Just update my trixie container.
builder@5ba2a4b665d9:~$ cat /etc/debian_version
trixie/sid
builder@5ba2a4b665d9:~$ dpkg --print-architecture
amd64
builder@5ba2a4b665d9:~$ dpkg --print-foreign-architectures
arm64
Using the cross compiler to arm64:
ii binutils-aarch64-linux-gnu:arm64 2.43.1-5
a
Processing control commands:
> severity -1 normal
Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross
compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"
Severity set to 'normal' from 'serious'
&g
Processing control commands:
> severity -1 normal
Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross
compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"
Ignoring request to change severity of Bug 1083135 to the sam
Control: severity -1 normal
Control: tags -1 + moreinfo
please provide a reproducible example what exactly doesn't work for you.
Package: gcc-14-aarch64-linux-gnu
Version: 14.2.0-3
Severity: serious
Justification: The compiler do not function at all.
X-Debbugs-Cc: erezge...@gmail.comm
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* Wha
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 #1073932 [libstdc++-14-dev] libstdc++-14-dev: 'using' specification results
in compiler error when specifying -fmodules-ts
Added tag(s) moreinfo.
--
1073932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073932
Debian
Maintainer,
* What led up to the situation?
When specifying a 'using' declaration the compiler produces an error when the
-fmodules-ts flag is used.
* What exactly did you do (or not do) that was effective (or
ineffective)?
The following program compiles correctly when -fmodul
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 #963564,
regarding gfortran: Internal error when processing pFUnit generated files with
--coverage
to be marked as done.
This means
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, 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 #966194,
regarding gcc-9: valgrind error: Conditional jump or move depends on
uninitialised value(s)
to be marked as done.
This
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 #951423,
regarding gunroar: symbol lookup error: gunroar: undefined symbol:
_D4core4stdc5errno5errnoFNbNdNiNeZi
to be marked as done
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 #951294,
regarding parsec47: exits with an error immediately after starting
to be marked as done.
This means that you claim that the
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
Package: libstdc++-14-dev
Version: 14-20240330-1
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
When specifying a 'using' declaration the compiler produces an error when the
-fmodules-ts flag is used.
* What exactly did you do (or not do
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.
Processing commands for cont...@bugs.debian.org:
> # assign from source to binary
> reassign 1051460 crowdsec-custom-bouncer
Bug #1051460 [src:crowdsec-custom-bouncer] crowdsec-custom-bouncer: move
systemd units to /usr
Bug reassigned from package 'src:crowdsec-custom-bouncer' to
'crowdsec-custo
Processing commands for cont...@bugs.debian.org:
> reassign 1072748 src:upower 1.90.3-1
Bug #1072748 [src:upower 1.90.3-1] upower: autopkgtest installed-tests is flaky
Warning: Unknown package '1.90.3-1'
Bug reassigned from package 'src:upower 1.90.3-1' to 'src:upower'.
Ignoring request to alter f
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
s
Added tag(s) trixie and sid.
> tags 1067912 + sid trixie
Bug #1067912 [src:nitrokey-app] Update Build-Depends for the time64 library
renames
Added tag(s) sid and trixie.
> tags 1067913 + sid trixie
Bug #1067913 [src:linssid] FTBFS: error: cannot convert ‘long int*’ to ‘const
time_t*’ {aka ‘c
gt; fi
> + dpkg --compare-versions 14-20240315-1 lt 14.1.0-5
> + cd gcc
> + patch -p1
> patching file debian/patches/pr113720.diff
> patching file debian/rules.patch
> Hunk #1 FAILED at 70.
> 1 out of 1 hunk FAILED -- saving rejects to file debian/rules.patch.rej
> make: *** [de
Processing control commands:
> tags -1 + moreinfo
Bug #1063882 [gcc] gcc: Internal error from ternary cond as inline asm parameter
Added tag(s) moreinfo.
--
1063882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
:r12));
please post the complete code example.
please also recheck with newer GCC versions (GCC 13, GCC 14) in newer
Debian development versions.
This generates an internal error:
$ g++ bug.cpp
during RTL pass: expand
bug.cpp: In function ‘void move(uint8_t, int64_t)’:
Processing control commands:
> severity 1061370 grave
Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel
Severity set to 'grave' from 'important'
> forcemerge -1 1061370
Bug #1062354 [libatomic1] libatomic1: 14-20240127-1 missing
libat_test_and_set_1_i2
Unable to merge bugs because:
package of #1061
Your message dated Sun, 3 Dec 2023 11:46:14 +0100
with message-id <47b2fd31-a79b-46af-b169-9b5e5cd14...@debian.org>
and subject line fixed in recent uploads
has caused the Debian Bug report #1032118,
regarding riscv64: error: too few arguments to function 'long u
Processing control commands:
> reassign -1 plplot
Bug #1055750 [gfortran] gfortran: [armhf] Yield SIGBUS when compiling with
-fstack-clash-protection
Bug reassigned from package 'gfortran' to 'plplot'.
No longer marked as found in versions 13.2.0-1.
Ignoring request to alter fixed versions of bug
Hi
On Sat, Oct 28, 2023 at 07:57:54PM +1300, rhys wrote:
> char myBuf[] = { '\x01', '\x04', '\x31', '\x00', '\x00', '\x1D', '\x7E',
> '\xF7' };
> printf ("sizeof (myBuf) = %d\n", sizeof (myBuf));
This is an array, so sizeof() shows the length of that array. Making it
longer would have showe
Please report this, where you downloaded that package versions, closing here in
Debian.
On 28.10.23 08:57, rhys wrote:
Package: gcc-12
Version: 12.2.0-14+rpi1
Severity: normal
X-Debbugs-Cc: rmor...@web.de
Dear Maintainer,
Following code:
#include
char myBuf[] = { '\x01', '\x04', '\x31', '
Your message dated Sat, 28 Oct 2023 13:28:37 +0200
with message-id
and subject line Re: Bug#1054891: gcc-12: sizeof() error in called function
has caused the Debian Bug report #1054891,
regarding gcc-12: sizeof() error in called function
to be marked as done.
This means that you claim that the
Package: gcc-12
Version: 12.2.0-14+rpi1
Severity: normal
X-Debbugs-Cc: rmor...@web.de
Dear Maintainer,
Following code:
#include
char myBuf[] = { '\x01', '\x04', '\x31', '\x00', '\x00', '\x1D', '\x7E', '\xF7'
};
void process_buffer (char *);
int main (int argc, char **argv) {
printf ("si
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
g piece of code generates a compiler error with gcc-12 in C++20
mode:
template
struct F {
static double foo() { return D; }
};
template
struct F {
static double foo() { return 1.0; }
};
int main()
{
return F::foo();
}
gcc-13 in sid does compile this correctly. on go
Package: gcc-12
Version: 12.3.0-10
Severity: normal
X-Debbugs-Cc: andre.nauj...@keysight.com
Hello.
The following piece of code generates a compiler error with gcc-12 in C++20
mode:
template
struct F {
static double foo() { return D; }
};
template
struct F {
static double foo
Processing commands for cont...@bugs.debian.org:
> notfound 1042082 3.08-1
Bug #1042082 {Done: Mark Hindley } [initscripts] Please take
over udev SysV init script
Bug #1052116 {Done: Mark Hindley } [initscripts] Removing
the udev init script breaks sysv bootup.
No longer marked as found in versi
Your message dated Fri, 18 Aug 2023 15:27:10 +
with message-id
and subject line Bug#1042960: fixed in gcc-doc-defaults 5:27
has caused the Debian Bug report #1042960,
regarding FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line
3 package 'gcc-doc'
s390 s390x sparc sparc64 x32 any
| make[1]: Leaving directory '/<>'
|dh_md5sums
|dh_builddeb
| dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3
package 'gcc-doc':
| 'Version' field value '5:': nothing after
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
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.
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
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 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
Your message dated Mon, 1 May 2023 09:47:10 +0200
with message-id
and subject line Re: gcc-arm-linux-gnueabihf: Compiling anything with
fails: error: '_Float128' is not supported on this target
has caused the Debian Bug report #1023692,
regarding gcc-arm-linux-gnueabihf: Compiling any
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
Processing commands for cont...@bugs.debian.org:
> merge 1021165 1022166
Bug #1021165 {Done: Aurelien Jarno } [src:glibc] armhf:
floatn-common.h:214:9: error: multiple types in one declaration
Unable to merge bugs because:
severity of #1022166 is 'normal' not 'grave'
Processing control commands:
> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108927
Bug #1032118 [src:gcc-snapshot] riscv64: error: too few arguments to function
'long unsigned int __riscv_vsetvlmax_e8mf8(void)'
Set Bug forwarded-to-address to
'https://gc
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108927
Control: tags -1 confirmed upstream patch
[PATCH] RISC-V: Remove void_type_node of void_args for vsetvlmax intrinsic
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612858.html
Source: gcc-snapshot
riscv64 intrisincs are currently broken.
% cat t.c
#include
int main()
{
size_t vl = __riscv_vsetvlmax_e8mf8();
return vl;
}
Gives:
g++ -march=rv64gcv1p0 t.c
t.c: In function 'int main()':
t.c:5:39: error: too few arguments to function 'lo
Processing control commands:
> reassign -1 libc6.1-dev 2.36-5
Bug #1021165 {Done: Matthias Klose } [src:gcc-snapshot] armhf:
floatn-common.h:214:9: error: multiple types in one declaration
Bug reassigned from package 'src:gcc-snapshot' to 'libc6.1-dev'.
Warning: Unkno
a51610ba7278d8fb426d84
In file included from /usr/include/stdio.h:430,
from p.cxx:1:
/usr/include/ia64-linux-gnu/bits/floatn.h:84:9: error: multiple types
in one declaration
84 | typedef __float128 _Float128;
| ^~
/usr/include/ia64-linux-gnu/bits/floatn
Your message dated Fri, 10 Feb 2023 13:46:25 +0300
with message-id
and subject line Re: Bug#968670: dwz: Fails with "Unknown DWARF DW_OP_1" (more
info needed)
has caused the Debian Bug report #968670,
regarding olive-editor: FTBFS: dh_dwz: error: dwz
-mdebian/olive-editor/usr/lib/
Your message dated Wed, 11 Jan 2023 01:11:19 +
with message-id <2670d6d3-60c9-481e-93a9-8e78e55d0...@debian.org>
and subject line Re: Bug#1026597: gcc-10-cross-ports: FTBFS: collect2: error:
ld returned 1 exit status
has caused the Debian Bug report #1026597,
regarding gcc-10-cross
Processing commands for cont...@bugs.debian.org:
> reassign 1026597 src:gcc-10
Bug #1026597 [src:gcc-10-cross-ports] gcc-10-cross-ports: FTBFS: collect2:
error: ld returned 1 exit status
Bug reassigned from package 'src:gcc-10-cross-ports' to 'src:gcc-10'.
No longer mark
Your message dated Sun, 8 Jan 2023 10:35:37 +0100
with message-id
and subject line fixed in glibc
has caused the Debian Bug report #1021165,
regarding armhf: floatn-common.h:214:9: error: multiple types in one declaration
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 3 Jan 2023 08:34:16 +0100
with message-id <53ccee3a-859e-ff20-51ae-78a9023ea...@ubuntu.com>
and subject line Re: gcc-10: FTBFS: mount.h:95:6: error: multiple definition of
'enum fsconfig_command'
has caused the Debian Bug report #1026530,
regarding gcc-10
ng gcc-12 FTBFS in unstable on amd64:
../../src/gcc/config/i386/i386.h:2356:10: fatal error: insn-attr-common.h: No
such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug
IRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings
> -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes
> -Wno-error=format-diag -Wold-style-definition -isystem ./include -fPIC -g
> -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -shared -nodefaultlibs
../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:75:
> /usr/include/linux/mount.h:95:6: error: multiple definition of 'enum
> fsconfig_command'
>95 | enum fsconfig_command {
> | ^~~~
> pwd: /<>/build/x86_64-linu
tst.o /tmp/tst.c
In file included from /tmp/tst.c:1:
/usr/include/math.h:27:10: fatal error: bits/libc-header-start.h: No such
file or directory
27 | #include
| ^~
compilation terminated.
Looking around, this was due to libc6-dev-armhf-cross not
Processing control commands:
> tags -1 + unreproducible
Bug #1023692 [gcc-arm-linux-gnueabihf] gcc-arm-linux-gnueabihf: Compiling
anything with fails: error: '_Float128' is not supported on this target
Added tag(s) unreproducible.
--
1023692: https://bugs.debian.org/cgi-bin/bugr
; #include
>
> Cross-compiling it doesn't work:
>
> $ arm-linux-gnueabihf-gcc-12 -c -o tst.o tst.c
>
> In file included from tst.c:1:
> /usr/include/bits/mathcalls-helper-functions.h:20:40: error: '_Float128' is
> not supported on this ta
1 - 100 of 1030 matches
Mail list logo
