From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 18C063858D33; Sat,  9 Sep 2023 13:26:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 18C063858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694266004;
	bh=pN24/aWLp/16eqWELAw2ynpYtte4wrTlZ/TS2Avm+ss=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tIIulUrCxWbsC5Pypu5Tbo6uhU2nw2y6xuMUNUKP82S04XaPnZelzELyAFXrwIZNQ
	 ZzYfc4rq8fSA9AZL1YNC9ugYUpxjQeGMHm5zE6LsTEB5iQS6IeBROPjNBvXDCzsGFh
	 gJeJB5GGVbEjDznf2htlp296+/dF+MLkJWomb17c=
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111353] bits/new_allocator.h: No such file or
 directory in freestanding C++ toolchain
Date: Sat, 09 Sep 2023 13:26:43 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: unlvsur at live dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111353-4-qCn2r7jmuf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111353-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111353-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111353

--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
what i am talking about is uninitialized memory for later initialization li=
ke
implementing containers for example

________________________________
From: redi at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Saturday, September 9, 2023 9:08
To: unlvsur@live.com <unlvsur@live.com>
Subject: [Bug libstdc++/111353] bits/new_allocator.h: No such file or direc=
tory
in freestanding C++ toolchain

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111353

--- 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 er=
ror
for some code (what code? where is the testcase? where is the `gcc -v` outp=
ut?)
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 ju=
st
stop bothering us with your terrible attempts at bug reports.

You can allocate memory in freestanding anyway, so what are you talking abo=
ut?


#include <new>
constexpr bool f()
{
  delete new int(0);
  return true;
}
static_assert( f() );

This compiles fine with -std=3Dc++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 wh=
at
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.=