From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Xi Ruoyao <xry111@mengyan1223.wang>
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc++-v3 failing to compile due to no matching function for call to ‘operator new(sizetype, sizetype)
Date: Mon, 2 May 2022 22:07:31 +1000 [thread overview]
Message-ID: <CAEYL+X_x=iTnstHS4ALiCgJPLCd25VPxvRjAbcsEbDevQ8m3DQ@mail.gmail.com> (raw)
In-Reply-To: <bb5ac2194e365624923bf48582b0808c3a0c7936.camel@mengyan1223.wang>
I've bisected the issue (which still happens with only
--enable-languages=c,c++ instead of --enable-languages=java),
and 0a0c2c3f06227d46b5e9542dfdd4e0fd2d67d894 is the first bad commit
apparently. I think I've done it wrong though, and
that 7a42b1fa1a090ead96cc0f94a8060a9650c810d5 is the breaking change.
Judging by the commit details, that seems likely, as it modifies what
appears to be relevant code. I wonder why it didn't break bootstrap on
upstream.
On Mon, May 2, 2022 at 8:24 PM Xi Ruoyao <xry111@mengyan1223.wang> wrote:
> 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 libstdc++-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 <xry111@mengyan1223.wang>
> > 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 ‘operator
> > > > 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:)
> > >
> > > Don't guess. Just build the unmodified trunk and if it fails
> > > reports to
> > > https://gcc.gnu.org/bugzilla.
>
> --
> Xi Ruoyao <xry111@mengyan1223.wang>
> School of Aerospace Science and Technology, Xidian University
>
next prev parent reply other threads:[~2022-05-02 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:20 Zopolis0
2022-05-02 9:29 ` Xi Ruoyao
2022-05-02 10:02 ` Zopolis0
2022-05-02 10:24 ` Xi Ruoyao
2022-05-02 12:07 ` Zopolis0 [this message]
2022-05-02 12:42 ` Xi Ruoyao
2022-05-03 5:30 ` Zopolis0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEYL+X_x=iTnstHS4ALiCgJPLCd25VPxvRjAbcsEbDevQ8m3DQ@mail.gmail.com' \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@mengyan1223.wang \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).