[Bug c++/95878] New: ICE when compiling code that mixes an empty class, [[no_unique_address]] and non-trivial default and copy constructors

2020-06-24 Thread boris.staletic at gmail dot com
Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: boris.staletic at gmail dot com Target Milestone: --- Hello, first, apologies for a bad title. I was unsure

[Bug c++/93711] [9/10/11 Regression] ICE: [[no_unique_address] when constructing via template helper

2020-07-01 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93711 --- Comment #7 from Boris Staletic --- I don't know if this is the same problem, since the actual `std::istream_iterator` isn't empty, unlike in the other test cases. If the following is a different problem, sorry up front for the noise. https:/

[Bug libstdc++/91067] New: Clang compiler can't link executable if std::filesystem::directory_iterator is encountered

2019-07-02 Thread boris.staletic at gmail dot com
IRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: boris.staletic at gmail dot com Target Milestone: --- When compiling with clang, a code that contains an object of the type std::files

[Bug libstdc++/91067] Clang compiler can't link executable if std::filesystem::directory_iterator is encountered

2019-07-02 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067 --- Comment #2 from Boris Staletic --- Created attachment 46549 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46549&action=edit Non-preprocessed file

[Bug libstdc++/91067] Clang compiler can't link executable if std::filesystem::directory_iterator is encountered

2019-07-02 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067 --- Comment #1 from Boris Staletic --- Created attachment 46548 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46548&action=edit Minimal reproducer - preprocessed with clang

[Bug c++/86422] New: G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-06 Thread boris.staletic at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: boris.staletic at gmail dot com Target Milestone: --- My gcc version is 8.1.0. I have not tried with the latest gcc snapshot. If requested, I will compile a

[Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-06 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 --- Comment #2 from Boris Staletic --- > so this time it's not parsing but code-generation that blows up things. That makes sense, when I was playing with the file, it took between 5 to 10 seconds to report syntax errors. Another thing that avo

[Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-06 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 --- Comment #4 from Boris Staletic --- I get the segmentations fault when running cc1plus directly. No matter if I pass -quiet or not. So what's the next step? Also, I have just noticed "Known to work: 8.1.1". Is that a mistake?

[Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-09 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 --- Comment #8 from Boris Staletic --- > ulimit -s unlimited After running that command and enabling swap, for a total of 16GB available memory, until about 5 minute mark, cc1plus was consuming >4GB. After about five minute mark, cc1plus started

[Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-09 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 --- Comment #10 from Boris Staletic --- Running "g++ -S -fno-exceptions CodePoint.cpp" didn't run into OOM killer, but gcc still hanged. The memory usage at maximum was 15.6GB. What I find strange is that "htop" reported the g++ process as dead m

[Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs

2018-07-09 Thread boris.staletic at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 --- Comment #12 from Boris Staletic --- If you're wondering about clang, it hangs too, but doesn't hog memory. > That's to be expected when it runs into swap. Anything else I should try?

[Bug c++/101000] New: ICE when trying to import the absl/container/flat_hash_map.h as a header module

2021-06-09 Thread boris.staletic at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: boris.staletic at gmail dot com Target Milestone: --- Steps to repro: 0. Install Abseil from https://github.com/abseil/abseil-cpp 1. g++ -std=c++20 -fmodules-ts -xc