[Bug bootstrap/117399] make all-target-libgcc fails because gcc/as line 114 is "exec $original" and $original is --64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117399 --- Comment #2 from Дилян Палаузов --- This was suggested here: https://stackoverflow.com/questions/22707265/how-to-build-libgcc-of-gcc-compiler/22707330#22707330 .

[Bug bootstrap/117396] gcc/configure --help should print --disable-multilib instead of --enable-multilib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117396 --- Comment #2 from Дилян Палаузов --- I think all of them (--disable-ld, --disable-ada, …) should be changed. This way ./configure --help will only suggest how to toggle the default and what is the default. Here a legthy discussion (by me):

[Bug web/117401] New: Spell that ./configure --enable-link-mutex is deprecated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117401 Bug ID: 117401 Summary: Spell that ./configure --enable-link-mutex is deprecated Product: gcc Version: 14.2.0 Status: UNCONFIRMED Severity: normal Pr

[Bug bootstrap/117399] New: make all-target-libgcc fails because gcc/as line 114 is "exec $original" and $original is --64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117399 Bug ID: 117399 Summary: make all-target-libgcc fails because gcc/as line 114 is "exec $original" and $original is --64 Product: gcc Version: 14.2.0 Status: UNCONFIRMED

[Bug bootstrap/117396] New: gcc/configure --help should print --disable-multilib instead of --enable-multilib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117396 Bug ID: 117396 Summary: gcc/configure --help should print --disable-multilib instead of --enable-multilib Product: gcc Version: 14.2.1 Status: UNCONFIRMED Seve

[Bug web/115183] New: GCCGO appears twice at https://gcc.gnu.org/onlinedocs/14.1.0/

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115183 Bug ID: 115183 Summary: GCCGO appears twice at https://gcc.gnu.org/onlinedocs/14.1.0/ Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 --- Comment #40 from Дилян Палаузов --- Makefile.in contains now: @if gcc-bootstrap @unless target-libbacktrace-bootstrap all-target-libgo: maybe-all-target-libbacktrace @endunless target-libbacktrace-bootstrap @endif gcc-bootstrap @unless gcc

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 --- Comment #36 from Дилян Палаузов --- > maybe this ought to be a `depend=` entry in Makefile.def instead? My understanding is that depend= only has effect for bootstrapped targets, and there is no boot_language=yes in gcc/go/config-lang.in.

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 --- Comment #34 from Дилян Палаузов --- Created attachment 57662 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57662&action=edit Proposed patch This fixes the problem. I do not understand the build system to say, that this is the best a

[Bug web/114223] New: Utilize filtering for git://gcc.gnu.org/git/gcc.git

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114223 Bug ID: 114223 Summary: Utilize filtering for git://gcc.gnu.org/git/gcc.git Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug c++/114220] False positive warning: possibly dangling reference to a temporary [-Wdangling-reference]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114220 --- Comment #3 from Дилян Палаузов --- > The warning is designed this way explictly because you are returning a > reference and taking a reference as an argument and in the case of b2, the > tempory is `std::string("u")` . > In GCC 14+ (since

[Bug c++/114220] False positive warning: possibly dangling reference to a temporary [-Wdangling-reference]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114220 --- Comment #2 from Дилян Палаузов --- Is my reading correct, that the warning is triggered, when a function receives as parameter a reference to a temporary and returns a reference? If this is the only criterion, then it is a wrong assumption,

[Bug c++/114220] New: False positive warning: possibly dangling reference to a temporary [-Wdangling-reference]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114220 Bug ID: 114220 Summary: False positive warning: possibly dangling reference to a temporary [-Wdangling-reference] Product: gcc Version: 13.2.1 Status: UNCONFIRMED

[Bug target/113679] long long minus double with gcc -m32 produces different results than other compilers or gcc -m64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 --- Comment #13 from Дилян Палаузов --- For clang being buggy from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679#c11 I filled https://github.com/llvm/llvm-project/issues/81358 .

[Bug target/113679] long long minus double with gcc -m32 produces different results than other compilers or gcc -m64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 --- Comment #8 from Дилян Палаузов --- -fexcess-precision=standard does not ensure consistent behaviour between gcc 13.2.1 20231205 (Red Hat 13.2.1-6) and clang 17.0.5. -msse2 -mfpmath=sse does for diff.c: #include #include int main(void) {

[Bug target/113679] long long minus double with gcc -m32 produces different results than other compilers or gcc -m64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 --- Comment #5 from Дилян Палаузов --- gcc -m64 -fexcess-precision=fast -o diff diff.c && ./diff 0.00 gcc -m32 -fexcess-precision=fast -o diff diff.c && ./diff -2.00 clang -m32 -fexcess-precision=fast -o diff diff.c && ./diff 0.00 cl

[Bug target/113679] long long minus double with gcc -m32 produces different results than other compilers or gcc -m64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 --- Comment #2 from Дилян Палаузов --- This happens only without optimizations: $ gcc -O0 -m32 -o diff diff.c && ./diff -2.00 $ gcc -O1 -m32 -o diff diff.c && ./diff 0.00 $ gcc -O2 -m32 -o diff diff.c && ./diff 0.00 $ gcc -O3 -m

[Bug c/113679] New: long long minus double with gcc -m32 produces different results than other compilers or gcc -m64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 Bug ID: 113679 Summary: long long minus double with gcc -m32 produces different results than other compilers or gcc -m64 Product: gcc Version: 13.2.1 Status: UNCONFIRMED

[Bug sanitizer/113123] New: ASAN_OPTIONS=log_to_syslog=true leads to deadlock

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113123 Bug ID: 113123 Summary: ASAN_OPTIONS=log_to_syslog=true leads to deadlock Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 Дилян Палаузов changed: What|Removed |Added CC||dilyan.palauzov at aegee dot org ---

[Bug go/106747] [12 Regression] Regression: go version does not print a number in 12.x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106747 --- Comment #5 from Дилян Палаузов --- (In reply to Ian Lance Taylor from comment #4) > This is fixed on tip. Want to backport the patch to the GCC 12 branch? This is a regression. It would be good if there is a correction on the GCC 12 branc

[Bug go/106747] Regression: go version does not print a number in 12.x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106747 --- Comment #3 from Дилян Палаузов --- installing gcc installs two binaries:gccgo and go. The first is OK: $ gccgo --version gccgo (GCC) 12.1.1 20220814 Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source fo

[Bug go/106747] New: Regression: go version does not print a number in 12.x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106747 Bug ID: 106747 Summary: Regression: go version does not print a number in 12.x Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 C

[Bug analyzer/105530] New: Analyzer makes wrong conclusions for the malloc (deallocator, ptr-index) attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105530 Bug ID: 105530 Summary: Analyzer makes wrong conclusions for the malloc (deallocator, ptr-index) attribute Product: gcc Version: 11.3.1 Status: UNCONFIRMED Sev

[Bug go/102469] New: gccgo: error: ‘copy’ defined as both imported name and global name, while golang does not produce this error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102469 Bug ID: 102469 Summary: gccgo: error: ‘copy’ defined as both imported name and global name, while golang does not produce this error Product: gcc Version: 11.2.

[Bug other/101834] New: make distclean forgets ./c++tools/

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101834 Bug ID: 101834 Summary: make distclean forgets ./c++tools/ Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other

[Bug libstdc++/101060] New: ‘fenv_t’ has not been declared in ‘::’ in 11.1, but is declared in 10.3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101060 Bug ID: 101060 Summary: ‘fenv_t’ has not been declared in ‘::’ in 11.1, but is declared in 10.3 Product: gcc Version: unknown Status: UNCONFIRMED Severity: nor