public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111680] DWARF information inconsistent with the generated RISC-V Binary Date: Tue, 03 Oct 2023 22:06:59 +0000 [thread overview] Message-ID: <bug-111680-4-jeVAJISWJg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111680-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111680 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-10-03 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually I take that back, it looks like the dwarf2 pass did do the wrong values as I don't think it is expecting 2 increments to the sp ...
next prev parent reply other threads:[~2023-10-03 22:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 16:11 [Bug debug/111680] New: DWARF information inconstant " king.chung at manchester dot ac.uk 2023-10-03 21:45 ` [Bug target/111680] DWARF information inconsistent " pinskia at gcc dot gnu.org 2023-10-03 21:46 ` pinskia at gcc dot gnu.org 2023-10-03 21:47 ` pinskia at gcc dot gnu.org 2023-10-03 21:59 ` pinskia at gcc dot gnu.org 2023-10-03 22:03 ` pinskia at gcc dot gnu.org 2023-10-03 22:06 ` pinskia at gcc dot gnu.org [this message] 2023-10-03 22:10 ` [Bug debug/111680] " pinskia at gcc dot gnu.org 2023-10-03 23:01 ` king.chung at manchester dot ac.uk 2023-10-03 23:11 ` 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-111680-4-jeVAJISWJg@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: linkBe 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).