public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/20403] dwarf-3: DW_MACINFO_define - wrong lineno fields for predefined macros Date: Thu, 10 Mar 2005 14:01:00 -0000 [thread overview] Message-ID: <20050310140149.18336.qmail@sourceware.org> (raw) In-Reply-To: <20050310130906.20403.niva@niisi.msk.ru> ------- Additional Comments From dberlin at gcc dot gnu dot org 2005-03-10 14:01 ------- This is technically correct. In 4.0 we are still off by a single line, we claim it to be line 1 when it should be 0. We also will output them after the main file starts (this is because of the order of CPP processing). However, this is an incredibly minor bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20403
next prev parent reply other threads:[~2005-03-10 14:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-10 13:09 [Bug debug/20403] New: dwarf2: " niva at niisi dot msk dot ru 2005-03-10 13:17 ` [Bug debug/20403] dwarf-3: " pinskia at gcc dot gnu dot org 2005-03-10 14:01 ` dberlin at gcc dot gnu dot org [this message] [not found] <bug-20403-5860@http.gcc.gnu.org/bugzilla/> 2008-08-07 21:35 ` tromey at gcc dot gnu dot org 2008-09-19 17:43 ` tromey at gcc dot gnu dot 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=20050310140149.18336.qmail@sourceware.org \ --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).