public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5112] c: Don't emit DEBUG_BEGIN_STMTs for K&R function argument declarations [PR105972]
Date: Wed, 11 Jan 2023 21:20:15 +0000 (GMT)	[thread overview]
Message-ID: <20230111212015.ED8763858C00@sourceware.org> (raw)

https://gcc.gnu.org/g:23b4ce18379cd336d99d7c71701be28118905b57

commit r13-5112-g23b4ce18379cd336d99d7c71701be28118905b57
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 11 22:18:42 2023 +0100

    c: Don't emit DEBUG_BEGIN_STMTs for K&R function argument declarations [PR105972]
    
    K&R function parameter declarations are handled by calling
    recursively c_parser_declaration_or_fndef in a loop, where each such
    call will add_debug_begin_stmt at the start.
    Now, if the K&R function definition is not a nested function,
    building_stmt_list_p () is false and so we don't emit the DEBUG_BEGIN_STMTs
    anywhere, but if it is a nested function, we emit it in the containing
    function at the point of the nested function definition.
    As the following testcase shows, it can cause ICEs if the containing
    function has var-tracking disabled but nested function has them enabled,
    as the DEBUG_BEGIN_STMTs are added to the containing function which
    shouldn't have them but MAY_HAVE_DEBUG_MARKER_STMTS is checked already
    for the nested function, or just wrong experience in the debugger.
    
    The following patch ensures we don't emit any such DEBUG_BEGIN_STMTs for the
    K&R function parameter declarations even in nested functions.
    
    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.

Diff:
---
 gcc/c/c-parser.cc               |  3 +++
 gcc/testsuite/gcc.dg/pr105972.c | 15 +++++++++++++++
 2 files changed, 18 insertions(+)

diff --git a/gcc/c/c-parser.cc b/gcc/c/c-parser.cc
index 3a5998007a9..3e2109bfd4f 100644
--- a/gcc/c/c-parser.cc
+++ b/gcc/c/c-parser.cc
@@ -2804,10 +2804,13 @@ c_parser_declaration_or_fndef (c_parser *parser, bool fndef_ok,
 	 declarator with a nonempty identifier list in a definition;
 	 and postfix attributes have never been accepted here in
 	 function definitions either.  */
+      int save_debug_nonbind_markers_p = debug_nonbind_markers_p;
+      debug_nonbind_markers_p = 0;
       while (c_parser_next_token_is_not (parser, CPP_EOF)
 	     && c_parser_next_token_is_not (parser, CPP_OPEN_BRACE))
 	c_parser_declaration_or_fndef (parser, false, false, false,
 				       true, false);
+      debug_nonbind_markers_p = save_debug_nonbind_markers_p;
       store_parm_decls ();
       if (omp_declare_simd_clauses)
 	c_finish_omp_declare_simd (parser, current_function_decl, NULL_TREE,
diff --git a/gcc/testsuite/gcc.dg/pr105972.c b/gcc/testsuite/gcc.dg/pr105972.c
new file mode 100644
index 00000000000..73f3385f7eb
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/pr105972.c
@@ -0,0 +1,15 @@
+/* PR c/105972 */
+/* { dg-do compile } */
+/* { dg-options "-O2 -g" } */
+
+__attribute__((optimize (0))) int
+foo (void)
+{
+  int
+  bar (x)
+    int x;
+  {
+    return x;
+  }
+  return bar (0);
+}

                 reply	other threads:[~2023-01-11 21:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230111212015.ED8763858C00@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@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).