public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111921] [11/12/13/14 Regression] ICE with nested function after an error since r6-205-g5c4abbb8e80153
Date: Wed, 01 Nov 2023 17:02:42 +0000	[thread overview]
Message-ID: <bug-111921-4-iKPHVFPoTn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111921-4@http.gcc.gnu.org/bugzilla/>

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11/12/13/14 Regression]    |[11/12/13/14 Regression]
                   |ICE with nested function    |ICE with nested function
                   |after an error              |after an error since
                   |                            |r6-205-g5c4abbb8e80153
           Keywords|needs-bisection             |
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Bisection finally found the relevant patch: r6-205-g5c4abbb8e80153

5c4abbb8e80153999b0298e4b2fe81d512f133c8 is the first bad commit
commit 5c4abbb8e80153999b0298e4b2fe81d512f133c8
Author: Marek Polacek <polacek@redhat.com>
Date:   Thu Apr 23 14:35:12 2015 +0000

    re PR c/65345 (ICE with _Generic selection on _Atomic int)

        PR c/65345
        * c-decl.c (set_labels_context_r): New function.
        (store_parm_decls): Call it via walk_tree_without_duplicates.
        * c-typeck.c (convert_lvalue_to_rvalue): Use create_tmp_var_raw
        instead of create_tmp_var.  Build TARGET_EXPR instead of
        COMPOUND_EXPR.
        (build_atomic_assign): Use create_tmp_var_raw instead of
        create_tmp_var.  Build TARGET_EXPRs instead of MODIFY_EXPR.

        * gcc.dg/pr65345-1.c: New test.
        * gcc.dg/pr65345-2.c: New test.

    From-SVN: r222370

Bisection actually needed a patch for bootstrap to succeed:

diff --git a/gcc/cp/cfns.gperf b/gcc/cp/cfns.gperf
index 68acd3d..5ecf86a 100644
--- a/gcc/cp/cfns.gperf
+++ b/gcc/cp/cfns.gperf
@@ -23,7 +23,7 @@ static unsigned int hash (const char *, unsigned int);
 #ifdef __GNUC__
 __inline
 #endif
-const char * libc_name_p (const char *, unsigned int);
+# const char * libc_name_p (const char *, unsigned int);
 %}
 %%
 # The standard C library functions, for feeding to gperf; the result is used
diff --git a/gcc/cp/cfns.h b/gcc/cp/cfns.h
index 1c6665d..ee38f6a 100644
--- a/gcc/cp/cfns.h
+++ b/gcc/cp/cfns.h
@@ -51,9 +51,6 @@ along with GCC; see the file COPYING3.  If not see
 __inline
 #endif
 static unsigned int hash (const char *, unsigned int);
-#ifdef __GNUC__
-__inline
-#endif
 const char * libc_name_p (const char *, unsigned int);
 /* maximum key range = 391, duplicates = 0 */

  parent reply	other threads:[~2023-11-01 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 10:37 [Bug c/111921] New: GCC: 14: internal compiler error: Segmentation fault 141242068 at smail dot nju.edu.cn
2023-10-22 16:17 ` [Bug middle-end/111921] [11/12/13/14 Regression] ICE with nested function after an error pinskia at gcc dot gnu.org
2023-10-22 16:44 ` pinskia at gcc dot gnu.org
2023-10-31 21:15 ` tkoenig at gcc dot gnu.org
2023-10-31 21:59 ` schwab@linux-m68k.org
2023-11-01 17:02 ` tkoenig at gcc dot gnu.org [this message]
2024-03-07 21:03 ` [Bug middle-end/111921] [11/12/13/14 Regression] ICE with nested function after an error since r6-205-g5c4abbb8e80153 law at gcc dot gnu.org
2024-03-12 13:23 ` jakub 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-111921-4-iKPHVFPoTn@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).