Re: libstdc++-v3 failing to compile due to no matching function for call to ‘operator new(sizetype, sizetype)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxx>
> > 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@xxxxxxxxxxxxxxxx>
> School of Aerospace Science and Technology, Xidian University
>




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux