From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Marek Polacek <polacek@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c: Don't emit DEBUG_BEGIN_STMTs for K&R function argument declarations [PR105972]
Date: Wed, 11 Jan 2023 20:26:03 +0000 [thread overview]
Message-ID: <ae8b90a2-9c93-95dc-b8a7-dd384666cbfd@codesourcery.com> (raw)
In-Reply-To: <Y776K/eRDes5Z0MD@tucnak>
On Wed, 11 Jan 2023, Jakub Jelinek via Gcc-patches wrote:
> The following patch ensures we don't emit any such DEBUG_BEGIN_STMTs for the
> K&R function parameter declarations even in nested functions.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2023-01-11 Jakub Jelinek <jakub@redhat.com>
>
> PR c/105972
> * c-parser.cc (c_parser_declaration_or_fndef): Disable debug non-bind
> markers for K&R function parameter declarations of nested functions.
>
> * gcc.dg/pr105972.c: New test.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-01-11 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 18:04 Jakub Jelinek
2023-01-11 20:26 ` Joseph Myers [this message]
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=ae8b90a2-9c93-95dc-b8a7-dd384666cbfd@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=polacek@redhat.com \
/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).