From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mengyan1223.wang (mengyan1223.wang [89.208.246.23]) by sourceware.org (Postfix) with ESMTPS id 19D2F3858D33 for ; Mon, 2 May 2022 10:24:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 19D2F3858D33 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: xry111@mengyan1223.wang) by mengyan1223.wang (Postfix) with ESMTPSA id 7C35766577; Mon, 2 May 2022 06:24:08 -0400 (EDT) Message-ID: Subject: Re: libstdc++-v3 failing to compile due to no matching function for call to =?gb2312?Q?=A1=AEoperator?= new(sizetype, sizetype) From: Xi Ruoyao To: Zopolis0 Cc: gcc-help@gcc.gnu.org Date: Mon, 02 May 2022 18:24:06 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.1 MIME-Version: 1.0 X-Spam-Status: No, score=-3028.6 required=5.0 tests=BAYES_00, CHARSET_FARAWAY_HEADER, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, KAM_SHORT, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2022 10:24:11 -0000 On Mon, 2022-05-02 at 20:02 +1000, Zopolis0 wrote: > The thing is, that builds fine, but I havent changed anything to do > with=C2=A0libstdc++-v3. Then maybe you've modified some compiler code common for languages and cause GCC to misbehave on libstdc++ code (then stage 1 libstdc++ fails), or maybe it causes GCC to miscompile itself and generate a compiler misbehaving on libstdc++ code (so stage 2 libstdc++ fails). Or maybe some modification to the building system causes libstdc++ built with wrong CXXFLAGS. Who knows? We have no idea how the code is modified. > On Mon, May 2, 2022 at 7:29 PM Xi Ruoyao > wrote: > > On Mon, 2022-05-02 at 19:20 +1000, Zopolis0 via Gcc-help wrote: > > > While trying to compile gcj, it breaks on a number of errors, many > > > of which > > > are along the lines of "no matching function for call to =E2=80=98ope= rator > > > new(sizetype, sizetype)". However, I have not touched this code, > > > and this > > > error does not appear on another branch which is a few months back > > > from > > > master. This leads me to believe that this is an error present on > > > master, > > > although I have not yet been able to locate the breaking commit. > > > (Example > > > of one such error:) > >=20 > > Don't guess.=C2=A0 Just build the unmodified trunk and if it fails > > reports to > > https://gcc.gnu.org/bugzilla. --=20 Xi Ruoyao School of Aerospace Science and Technology, Xidian University