public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/44652] Column numbers in error messages are wrong
Date: Thu, 24 Jun 2010 12:03:00 -0000 [thread overview]
Message-ID: <20100624120307.13641.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44652-15241@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from manu at gcc dot gnu dot org 2010-06-24 12:03 -------
(In reply to comment #3)
> I think column 0 is correct for the start of all preprocessor directives.
But the #include does not start at column 0, so there is something wrong there.
We know that libcpp column information sucks in many places. Tom and I have
several patches but we never got around to finish them.
To not get column info just use -fno-show-column
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2010-06-24 12:03:06
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44652
next prev parent reply other threads:[~2010-06-24 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 8:29 [Bug preprocessor/44652] New: " hariharans at picochip dot com
2010-06-24 8:30 ` [Bug preprocessor/44652] " hariharans at picochip dot com
2010-06-24 8:31 ` hariharans at picochip dot com
2010-06-24 8:34 ` pinskia at gcc dot gnu dot org
2010-06-24 12:03 ` manu at gcc dot gnu dot org [this message]
[not found] <bug-44652-4@http.gcc.gnu.org/bugzilla/>
2021-09-02 1:48 ` pinskia at gcc dot gnu.org
2021-09-02 1:52 ` pinskia at gcc dot gnu.org
2021-09-02 2:07 ` 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=20100624120307.13641.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: 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).