From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Martin Jambor <mjambor@suse.cz>
Cc: Jan Hubicka <hubicka@ucw.cz>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] ipa: Self-DCE of uses of removed call LHSs (PR 108007)
Date: Thu, 5 Oct 2023 01:08:05 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2310042310490.12345@angie.orcam.me.uk> (raw)
In-Reply-To: <ri61qebk536.fsf@suse.cz>
On Tue, 3 Oct 2023, Martin Jambor wrote:
> > SSA graph may be deep so this may cause stack overflow, so I think we
> > should use worklist here (it is also easy to do).
> >
> > OK with that change.
> > Honza
>
> I have just committed the following after a bootstrap and testing on
> x86_64-linux.
This has regressed the native `powerpc64le-linux-gnu' configuration,
which doesn't bootstrap here anymore:
Comparing stages 2 and 3
Bootstrap comparison failure!
powerpc64le-linux-gnu/libstdc++-v3/src/compatibility-ldbl.o differs
powerpc64le-linux-gnu/libstdc++-v3/src/.libs/compatibility-ldbl.o differs
I have double-checked this is indeed the offending commit, the compiler
bootstraps just fine as at commit 7eb5ce7f58ed ("Remove pass counting in
VRP.").
Shall I file a PR, or can you handle it regardless? Let me know if you
need anything from me.
Maciej
next prev parent reply other threads:[~2023-10-05 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:45 Martin Jambor
2023-05-12 19:21 ` Bernhard Reutner-Fischer
2023-06-13 15:11 ` Martin Jambor
2023-06-15 9:20 ` Bernhard Reutner-Fischer
2023-09-01 13:32 ` Martin Jambor
2023-09-19 11:36 ` Martin Jambor
2023-09-25 8:52 ` Jan Hubicka
2023-10-03 17:07 ` Martin Jambor
2023-10-05 0:08 ` Maciej W. Rozycki [this message]
2023-10-05 0:09 ` Andrew Pinski
2024-01-16 12:39 Martin Jambor
2024-01-22 17:21 ` Jan Hubicka
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=alpine.DEB.2.21.2310042310490.12345@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
/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).