public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66290] wrong location for -Wunused-macros
Date: Sun, 31 Jul 2022 12:13:53 +0000	[thread overview]
Message-ID: <bug-66290-4-WlpHz5gLIg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66290-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66290

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Lewis Hyatt <lhyatt@gcc.gnu.org>:

https://gcc.gnu.org/g:b04c399e258e686dddad879bf7e27d9e28fd6fde

commit r13-1903-gb04c399e258e686dddad879bf7e27d9e28fd6fde
Author: Lewis Hyatt <lhyatt@gmail.com>
Date:   Tue Jul 12 09:47:47 2022 -0400

    c++: Fix location for -Wunused-macros [PR66290]

    In C++, since all tokens are lexed from libcpp up front, diagnostics
generated
    by libcpp after lexing has completed do not get a valid location from
libcpp
    (rather, libcpp thinks they all pertain to the end of the file.) This has
long
    been addressed using the global variable "done_lexing", which the C++
frontend
    sets at the appropriate time; when done_lexing is true, then
c_cpp_diagnostic(),
    which outputs libcpp's diagnostics, uses input_location instead of the
wrong
    libcpp location. The C++ frontend arranges that input_location will point
to the
    token it is currently processing, so this generally works fine. However,
there
    is one exception currently, which is -Wunused-macros. This gets generated
at the
    end of processing in cpp_finish (), since we need to wait until then to
    determine whether a macro was eventually used or not. But the locations it
    passes to c_cpp_diagnostic () were remembered from the original lexing and
hence
    they should not be overridden with input_location, which is now the one
    incorrectly pointing to the end of the file.

    Fixed by setting done_lexing=false again just prior to calling cpp_finish
(). I
    also renamed the variable from done_lexing to "override_libcpp_locations",
since
    it's now not strictly about lexing anymore.

    There is no new testcase with this patch, since we already had an xfailed
    testcase which is now fixed.

    gcc/c-family/ChangeLog:

            PR c++/66290
            * c-common.h: Rename global done_lexing to
            override_libcpp_locations.
            * c-common.cc (c_cpp_diagnostic): Likewise.
            * c-opts.cc (c_common_finish): Set override_libcpp_locations
            (formerly done_lexing) immediately prior to calling cpp_finish ().

    gcc/cp/ChangeLog:

            PR c++/66290
            * parser.cc (cp_lexer_new_main): Rename global done_lexing to
            override_libcpp_locations.

    gcc/testsuite/ChangeLog:

            PR c++/66290
            * c-c++-common/pragma-diag-15.c: Remove xfail for C++.

  parent reply	other threads:[~2022-07-31 12:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 12:06 [Bug c++/66290] New: " manu at gcc dot gnu.org
2022-07-11 21:53 ` [Bug c++/66290] " lhyatt at gcc dot gnu.org
2022-07-12 13:40 ` lhyatt at gcc dot gnu.org
2022-07-28 14:15 ` lhyatt at gcc dot gnu.org
2022-07-31 12:13 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-31 12:15 ` lhyatt at gcc dot gnu.org
2022-08-05 16:17 ` lhyatt at gcc dot gnu.org
2023-06-20 22:04 ` cvs-commit at gcc dot gnu.org
2023-06-20 22:05 ` lhyatt 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-66290-4-WlpHz5gLIg@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).