public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dblaikie at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/60815] Inconsistent prologue line table location Date: Fri, 11 Apr 2014 00:44:00 -0000 [thread overview] Message-ID: <bug-60815-4-grFUjCdmxD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60815-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60815 --- Comment #1 from David Blaikie <dblaikie at gmail dot com> --- Oh - and if we can confirm the direction you're going with this (if the decision is that the prologue should start, like Clang, at the opening '{' always, for example) I'll go ahead and update the GDB test suite to either be agnostic or to KFAIL those tests under GDB, referencing this bug.
next prev parent reply other threads:[~2014-04-11 0:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-11 0:35 [Bug debug/60815] New: " dblaikie at gmail dot com 2014-04-11 0:44 ` dblaikie at gmail dot com [this message] 2014-04-11 9:07 ` [Bug c++/60815] " rguenth at gcc dot gnu.org 2021-08-27 19:30 ` [Bug c++/60815] prologue line is wrong for templates 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-60815-4-grFUjCdmxD@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).