public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/52998] caret and -ftrack-macro-expansion don't mix well
Date: Sun, 15 Apr 2012 20:38:00 -0000	[thread overview]
Message-ID: <bug-52998-4-SUltjkl7mp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52998-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52998

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-15 20:37:44 UTC ---
(In reply to comment #1)
> I think with and without macro expansion, the error should be given at 13:3,
> and unwind from outermost to innermost. Innermost to outermost makes sense if
> we show preprocessed lines:
> 
> macro-caret.c:5:14: error: invalid operands to binary << (have ‘double’ and
> ‘int’)
>    1.0 << 1
>        ^

But with preprocessed source lines, the best location is 5:14, because this way
the user can compare what is in that line with the preprocessed line shown by
GCC. So, in some sense, cc1 is right, and cc1plus is wrong.


  parent reply	other threads:[~2012-04-15 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 20:21 [Bug preprocessor/52998] New: " manu at gcc dot gnu.org
2012-04-15 20:35 ` [Bug preprocessor/52998] " manu at gcc dot gnu.org
2012-04-15 20:38 ` manu at gcc dot gnu.org [this message]
2012-04-24  4:37 ` pinskia at gcc dot gnu.org
2012-04-30 17:28 ` [Bug preprocessor/52998] different macro unwinder for C and C++ (-ftrack-macro-expansion) manu at gcc dot gnu.org
2021-08-02  3:35 ` 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-52998-4-SUltjkl7mp@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: 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).