public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/56154] New: [4.7/4.8 Regression] Bad .debug_loc generated for some code Date: Wed, 30 Jan 2013 15:53:00 -0000 [thread overview] Message-ID: <bug-56154-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56154 Bug #: 56154 Summary: [4.7/4.8 Regression] Bad .debug_loc generated for some code Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: jakub@gcc.gnu.org ReportedBy: jakub@gcc.gnu.org Since http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175076 without inline asm, but with inline asm even before, we can end up with a .debug_loc location list which for the first function in .text starts with 0, 0 entry. See https://bugzilla.redhat.com/show_bug.cgi?id=904252 for more details.
next reply other threads:[~2013-01-30 15:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-30 15:53 jakub at gcc dot gnu.org [this message] 2013-01-30 17:17 ` [Bug debug/56154] " jakub at gcc dot gnu.org 2013-01-30 17:22 ` jakub at gcc dot gnu.org 2013-02-07 14:49 ` jakub at gcc dot gnu.org 2013-02-07 15:19 ` [Bug debug/56154] [4.7 " jakub at gcc dot gnu.org 2013-04-03 9:50 ` rguenth at gcc dot gnu.org 2013-04-11 7:59 ` rguenth at gcc dot gnu.org 2014-06-12 13:22 ` rguenth 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-56154-4@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).