https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #7 from Jonathan Wakely ---
(In reply to Robert Durkacz from comment #3)
> So I guess the compiler just does not address this particular kind of use
> case but it seems to me that, on the contrary, there should be a compilation
> cap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #5 from Robert Durkacz ---
That is a good idea.
On Sun, 10 Jul 2022 at 19:56, redi at gcc dot gnu.org <
gcc-bugzi...@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
>
> --- Comment #4 from Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #4 from Jonathan Wakely ---
Yes, like https://wg21.link/p1967r7
But in the meantime, you can create a static array of trivial types (not
std::string) and then iterate over it at runtime to copy the values into the
data structure yo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #3 from Robert Durkacz ---
The suggestions from Johnathon Wakely would work but it is changing the
problem. Rather than using simple types, the application is aimed at using more
elaborate types (std:multimap).
My reason for thinking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #2 from Jonathan Wakely ---
(In reply to Robert Durkacz from comment #0)
> My personal interest in reporting this as a
> bug, whether it is or not, is to get any advice what is a better way to do
> what I am trying to do.
Get more m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #1 from Andreas Schwab ---
That's the OOM killer.
