https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120418
Alexey changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120418
--- Comment #3 from Alexey ---
I use dejagnu 1.6.3 for testing. And they fails in this way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120418
--- Comment #1 from Alexey ---
I found this issue because failures appeared when testing a toolchain. I wonder
why these tests are not failing for others?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120418
Bug ID: 120418
Summary: embed testcases issue
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120376
--- Comment #2 from Alexey ---
Sorry, it seems obvious to set it to 0.
It looks like the available range must be fixed in the GCC source code then.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120376
Bug ID: 120376
Summary: -fmalloc-dce=0 is not work as expected
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117977
Bug ID: 117977
Summary: duplicated warnings output
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117550
Bug ID: 117550
Summary: constexpr inlining and size optimizations
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117550
--- Comment #4 from Alexey ---
Yes, it seems this task is a duplicate of bug 93008. However, my request is to
have acceptable behavior only for the -Os optimization.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117550
--- Comment #3 from Alexey ---
Testcase is:
```
#include
std::string my_string;
void append_my_string(const char *foo) {
my_string.append(foo);
}
```
https://godbolt.org/z/vTE1z7h46
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116054
--- Comment #4 from Alexey ---
The issue because of change is
https://github.com/gcc-mirror/gcc/commit/d8a6945c6ea22efa4d5e42fe1922d2b27953c8cd
But after I reverted it the result size for the real application grew a bit :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
--- Comment #4 from Alexey ---
> Don't do that then ;-)
I would like to not do this :)
But expecting that simple code able to be compiled after the upgrade :D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
--- Comment #1 from Alexey ---
To reproduce compile with options "-std=gnu++14 -fconcepts"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
Bug ID: 116070
Summary: broken headers for compile with flags -std=gnu++14
-fconcepts
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116054
Bug ID: 116054
Summary: RISCV: RV32: prologue/epilogue degradation
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115784
--- Comment #2 from Alexey ---
Hi David, thank you for a quick reply!
Maybe it does not critical for high-level applications, that usually don't use
"noreturn" functions.
In embedded world, it's a common practice to send a reset signal and inv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115784
Bug ID: 115784
Summary: -Wanalyzer-infinite-loop does not take into account
noreturn attribute
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115015
Bug ID: 115015
Summary: libstdc++ build with '-fno-rtti' is broken
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109131
Alexey changed:
What|Removed |Added
CC||alexey.lapshin at espressif
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111558
Bug ID: 111558
Summary: RISCV: shrink-wrapper optimization question
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111372
--- Comment #3 from Alexey ---
Ok, but it's better to have configure option or something else just for
toolchains that definitely do not use vector extension
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111372
Bug ID: 111372
Summary: libgcc: RISCV C++ exception handling stack usage grew
in 13.1
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111099
Bug ID: 111099
Summary: -fanalyzer -Os segmentation fault
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
23 matches
Mail list logo
