public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/102649] GCC 9.3.1 LTO bug -- incorrect function call, bad stack arguments pushed
Date: Tue, 12 Oct 2021 13:10:48 +0000	[thread overview]
Message-ID: <bug-102649-4-okY05T4VL7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102649-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
All right, so being in the described situation I would recommend the following
steps:

1) please try bisecting GCC revisions and find the first on that fixed the
issue in between version 9.x and 10.x release. That would tell us more.

2) You can experiment with -fno-lto, which you can use for a subset of object
files (the rest will be built with LTO). Doing that, you will be able to
isolate that to a minimal set of objects that need -flto in order to expose the
issue.

3) You can use -fdump-tree-all for LTO linking step and you can investigate if
the caller really calls the function with an argument being set to 0.

  parent reply	other threads:[~2021-10-12 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 13:38 [Bug lto/102649] New: " davidhaufegcc at gmail dot com
2021-10-09  1:49 ` [Bug lto/102649] " pinskia at gcc dot gnu.org
2021-10-11 17:12 ` davidhaufegcc at gmail dot com
2021-10-12 13:10 ` marxin at gcc dot gnu.org [this message]
2024-04-13  1:05 ` pinskia at gcc dot gnu.org

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-102649-4-okY05T4VL7@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).