[Bug c++/94184] Global variable inline constructor elision.

2022-10-17 Thread trass3r at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94184 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #2 from

[Bug c++/107292] New: no warning for unused std::error_code

2022-10-17 Thread trass3r at gmail dot com via Gcc-bugs
++ Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- #include void foo() { std::error_code ec; } The code does get optimized away as system_category() is [[gnu::const]] but there is no -Wunused warning. https://godbolt.org/z

[Bug middle-end/32911] Function __attribute__ ((idempotent))

2021-09-04 Thread trass3r at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #7 from

[Bug tree-optimization/93540] Attributes pure and const not working with aggregate return types, even trivial ones

2021-09-04 Thread trass3r at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93540 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #2 from

[Bug c/88566] -Wconversion not using value range information

2020-11-13 Thread trass3r at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88566 Trass3r changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug analyzer/96659] New: error: cast from 'const ana::region*' to 'long int' loses precision in store.h

2020-08-17 Thread trass3r at gmail dot com
D Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- x86_64-w64-mingw32-g++ -fno-PIE -c -O3 -g -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-

[Bug debug/80490] -gsplit-dwarf: top namespace info seems to be lost in GDB

2020-07-22 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80490 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #6 from

[Bug c/12245] [8/9/10/11 regression] Uses lots of memory when compiling large initialized arrays

2020-05-26 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12245 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #77 from

[Bug pch/95131] Instantiate templates at pch generation time

2020-05-15 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95131 --- Comment #3 from Trass3r --- Well sure but most existing codebases won't be ported to modules because of the effort while enabling pch is now straightforward with latest CMake. These conformance issues have also been identified in https://rev

[Bug pch/95131] New: Instantiate templates at pch generation time

2020-05-14 Thread trass3r at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- Judging by the limited information -ftime-report provides it looks like gcc still spends quite some time on things that could have been done at pch generation time already like

[Bug target/94576] Regression build newlib for Arm

2020-04-21 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94576 Trass3r changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug target/94576] Regression build newlib for Arm64

2020-04-14 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94576 --- Comment #4 from Trass3r --- Created attachment 48268 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48268&action=edit preprocessed source It's -march=armv8.1-m.main+mve. arm-none-eabi is just the configured target name which hasn't bee

[Bug target/94576] Regression build newlib for Arm64

2020-04-13 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94576 --- Comment #1 from Trass3r --- Looks like it also happens with newlib-3.3: https://github.com/Trass3r/bleeding-edge-toolchain/runs/582133302

[Bug target/94576] New: Regression build newlib for Arm64

2020-04-13 Thread trass3r at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- https://github.com/Trass3r/bleeding-edge-toolchain/runs/581839696 arm-none-eabi-gcc -B/mnt/host/buildNative/newlib-3.1.0-nano/arm-none-eabi/thumb/v8.1-m.main+mve/hard/newlib/ -isystem

[Bug c++/64867] split warning for passing non-POD to varargs function from -Wconditionally-supported into new warning flag, -Wnon-pod-varargs

2020-01-25 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64867 --- Comment #29 from Trass3r --- Ah I see, ok.

[Bug c++/64867] split warning for passing non-POD to varargs function from -Wconditionally-supported into new warning flag, -Wnon-pod-varargs

2020-01-25 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64867 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #27 from

[Bug c/93252] Warning for symbols that could be internalized

2020-01-13 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93252 --- Comment #2 from Trass3r --- Yeah it's in the same vein as the other -Wsuggest warnings which run during lto. Like a.c void f() {} // can be made static void g() { f(); } b.c void g(); int main() { g(); }

[Bug c/93252] New: Warning for symbols that could be internalized

2020-01-13 Thread trass3r at gmail dot com
: c Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- Similar to -Wsuggest-final it would be nice to have a warning that identifies functions that could be marked static (resp. anonymous namespaces for classes in C++).

[Bug other/92396] -ftime-trace support

2019-11-07 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92396 --- Comment #4 from Trass3r --- Nice! Btw the traces can be viewed independently of the browser using https://www.speedscope.app.

[Bug other/92396] New: -ftime-trace support

2019-11-06 Thread trass3r at gmail dot com
: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- Would be nice if gcc also supported clang's -ftime-trace option for optimizing compile times: https://www.snsystems.com/technology/tech-blog/clang-time-trace-feature

[Bug middle-end/92037] [10 Regression] LTO bootstrap broken in selftests

2019-10-09 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92037 Trass3r changed: What|Removed |Added CC||trass3r at gmail dot com --- Comment #2 from

[Bug tree-optimization/91986] New: missed loop unrolling optimization

2019-10-03 Thread trass3r at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- #include #include const int N = 4; void bitreverse(int* data) { uint32_t j = 0; for (uint32_t i = 0; i < N; ++i) { if (j > i) std::swa

[Bug tree-optimization/91901] unchanged stack array not optimized away in favor off constant pool entry

2019-09-26 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91901 --- Comment #2 from Trass3r --- (In reply to Richard Biener from comment #1) > The compiler doesn't know that printf doesn't modify the data you pass it to > so it cannot elide the automatic variable. Does it matter in this case? The data comes

[Bug tree-optimization/91901] New: constexpr stack array not optimized away

2019-09-25 Thread trass3r at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: trass3r at gmail dot com Target Milestone: --- Created attachment 46940 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46940&action=edit full test code #include <https://github.com/Neargye/magi

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-08-12 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #27 from Trass3r --- (In reply to rguent...@suse.de from comment #25) > I fear this is the libbfd dwarf reader simply not coping with > DW_AT_abstract_origin in other CUs, being confused as to which > abbrev section it needs to look i

[Bug c++/68901] UBSan triggers false -Wpadded warning

2019-06-01 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68901 --- Comment #10 from Trass3r --- Yeah short on time. (plus the testsuite can't be run properly in WSL due to stack overflows: https://github.com/microsoft/WSL/issues/633) Feel free to pick up the patch. Any comments on ARTIFICIAL not being used