public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davidhaufegcc at gmail dot com" <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: Mon, 11 Oct 2021 17:12:34 +0000	[thread overview]
Message-ID: <bug-102649-4-3vj2PdAj9s@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 #2 from David Haufe <davidhaufegcc at gmail dot com> ---
I had assumed this would be the response. Unfortunately the source code
involved is both large (1000+ object files in this build) and proprietary. The
behavior we see where if we roll forward GIT and rebuild, and unrelated changes
"fix" the problem, makes it seem futile to develop an isolated test case. 

I can provide the assembly for the functions that highlight the error if that
would be beneficial? Not sure how helpful that would be though. Are there any
other best practices in a case like this one?

  parent reply	other threads:[~2021-10-11 17:12 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 [this message]
2021-10-12 13:10 ` marxin at gcc dot gnu.org
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-3vj2PdAj9s@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).