[Bug tree-optimization/83389] std::tie generates sub-optimal code when used to compare POD fields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83389 --- Comment #4 from Luca Stoppa --- (In reply to Jonathan Wakely from comment #2) > This isn't a libstdc++ bug. std::tie is doing exactly what it's meant to do, > which is generate a tuple of references, so of course it's not the same as > compar

[Bug libstdc++/83389] std::tie generates sub-optimal code when used to compare POD fields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83389 --- Comment #1 from Luca Stoppa --- Created attachment 42846 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42846&action=edit Generated assembler file The code was compiled with g++ -std=c++17 -O3 -S sample.cpp g++ --version: g++ (GCC) 7.

[Bug libstdc++/83389] New: std::tie generates sub-optimal code when used to compare POD fields

Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: lucanus81 at gmail dot com Target Milestone: --- Created attachment 42845 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42845&action=edit cpp file with the example

[Bug c++/78491] invalid conversion from 'const void*' to 'void*'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78491 --- Comment #2 from Luca Stoppa --- Just wanted to add that changing the vector element from "const std::string" to "std::string" seems to fix this issue.

[Bug c++/78491] invalid conversion from 'const void*' to 'void*'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78491 --- Comment #1 from Luca Stoppa --- Created attachment 40126 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40126&action=edit full error message

[Bug c++/78491] New: invalid conversion from 'const void*' to 'void*'

Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lucanus81 at gmail dot com Target Milestone: --- Created attachment 40125 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40125&action=edit test case when compiling the testcase attached her

[Bug c++/78399] g++ generates sub-optimal assembler code when structs aren't explicitly aligned.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78399 --- Comment #1 from Luca Stoppa --- Created attachment 40071 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40071&action=edit Optimal code

[Bug c++/78399] New: g++ generates sub-optimal assembler code when structs aren't explicitly aligned.

erity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lucanus81 at gmail dot com Target Milestone: --- Created attachment 40070 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40070&action=edit suboptimal co

[Bug c++/78391] g++ (any version) at O0 (for O1, O2, O3 is ok) doesn't warn when class members are used uninitialized.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78391 --- Comment #2 from Luca Stoppa --- (In reply to Richard Biener from comment #1) > -Wuninitialized requires optimization to handle this case. I see thanks. Considering that I found this bug in our unit tests, I'll simply add -O1 in order to avoi

[Bug c++/78391] New: g++ (any version) at O0 (for O1, O2, O3 is ok) doesn't warn when class members are used uninitialized.

tatus: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lucanus81 at gmail dot com Target Milestone: --- Created attachment 40063 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40063&