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/91669] #pragma's and _Pragma's work but _Pragma's used in an equivalent macro don't
Date: Tue, 04 Oct 2022 01:29:28 +0000	[thread overview]
Message-ID: <bug-91669-4-ERTk0DTX3H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91669-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:70e3f71a279856eabf99bbc92c0345c3ad20b615

commit r13-3051-g70e3f71a279856eabf99bbc92c0345c3ad20b615
Author: Lewis Hyatt <lhyatt@gmail.com>
Date:   Sat Oct 1 12:05:13 2022 -0400

    diagnostics: Add test for fixed _Pragma location issue [PR91669]

    This PR related to _Pragma locations and diagnostic pragmas was fixed by a
    combination of r10-325 and r13-1596. Add missing test coverage.

    gcc/testsuite/ChangeLog:

            PR c/91669
            * c-c++-common/pr91669.c: New test.

  parent reply	other threads:[~2022-10-04  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91669-4@http.gcc.gnu.org/bugzilla/>
2021-10-29 16:25 ` burnus at gcc dot gnu.org
2021-10-29 17:40 ` burnus at gcc dot gnu.org
2022-09-30 23:00 ` lhyatt at gcc dot gnu.org
2022-10-04  1:29 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-04  1:34 ` lhyatt at gcc dot gnu.org
2022-10-19 20:29 ` 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-91669-4-ERTk0DTX3H@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).