public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alvin at alvinhc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108040] -fdevirtualize causes part of function to be missing in output
Date: Fri, 28 Apr 2023 12:35:54 +0000	[thread overview]
Message-ID: <bug-108040-4-mcmNyTnz0K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108040-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Alvin Wong <alvin at alvinhc dot com> ---
Thanks for trying to look into the issue. The error you got looks like an
effect of
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=87235f1e5c740de9c6f72a5dd7d7eb9cb7df2e1d
that is not in GCC 12. I guess I can retest with GCC 13 but I don't have it
yet, so it will have to wait.

On simplifying the test case, I'm guessing I probably can't do much about that,
but, uh, I can maybe give it a try some time (no promises).

      parent reply	other threads:[~2023-04-28 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 22:01 [Bug c++/108040] New: " alvinhochun at gmail dot com
2023-04-28 11:29 ` [Bug ipa/108040] " jamborm at gcc dot gnu.org
2023-04-28 12:35 ` alvin at alvinhc dot com [this message]

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=bug-108040-4-mcmNyTnz0K@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).