https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111353
--- Comment #3 from cqwrteur <unlvsur at live dot com> --- what i am talking about is uninitialized memory for later initialization like implementing containers for example ________________________________ From: redi at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> Sent: Saturday, September 9, 2023 9:08 To: unlv...@live.com <unlv...@live.com> Subject: [Bug libstdc++/111353] bits/new_allocator.h: No such file or directory in freestanding C++ toolchain https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111353 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- This is not a proper bug report. What are you reporting, that you get an error for some code (what code? where is the testcase? where is the `gcc -v` output?) or that you want a new feature to support something that isn't currently supported? Just pasting a compiler error with no context IS USELESS. Try harder, or just stop bothering us with your terrible attempts at bug reports. You can allocate memory in freestanding anyway, so what are you talking about? #include <new> constexpr bool f() { delete new int(0); return true; } static_assert( f() ); This compiles fine with -std=c++20 -ffreestanding Maybe you mean you can't use operator new(size_t), but you didn't say that, because as usual your bug reports are terrible and force people to guess what the problem is. Try harder, or go away. -- You are receiving this mail because: You reported the bug. You are on the CC list for the bug.
