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/97882] [8/9/10/11 Regression] Segmentation Fault on improper redeclaration of function
Date: Thu, 04 Feb 2021 21:54:03 +0000 [thread overview]
Message-ID: <bug-97882-4-Ydk7HjAgHO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97882-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97882
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:ce5720447c69286599b96bae53ae854b1bbe41fa
commit r11-7107-gce5720447c69286599b96bae53ae854b1bbe41fa
Author: Martin Sebor <msebor@redhat.com>
Date: Thu Feb 4 14:50:23 2021 -0700
PR c/97882 - Segmentation Fault on improper redeclaration of function
gcc/c/ChangeLog:
PR c/97882
* c-decl.c (locate_old_decl): Add type to diagnostic output.
(diagnose_mismatched_decls): Same.
(start_function): Introduce temporaries for better readability.
* c-typeck.c (comptypes_internal): Only consider complete enum
types in comparisons with integers.
gcc/testsuite/ChangeLog:
PR c/97882
* gcc.dg/decl-8.c: Adjust text of expected diagnostic.
* gcc.dg/label-decl-4.c: Same.
* gcc.dg/mismatch-decl-1.c: Same.
* gcc.dg/old-style-then-proto-1.c: Same.
* gcc.dg/parm-mismatch-1.c: Same.
* gcc.dg/pr35445.c: Same.
* gcc.dg/redecl-11.c: Same.
* gcc.dg/redecl-12.c: Same.
* gcc.dg/redecl-13.c: Same.
* gcc.dg/redecl-15.c: Same.
* gcc.dg/tls/thr-init-1.c: Same.
* objc.dg/id-1.m: Same.
* objc.dg/tls/diag-3.m: Same.
* gcc.dg/pr97882.c: New test.
* gcc.dg/qual-return-7.c: New test.
* gcc.dg/qual-return-8.c: New test.
next prev parent reply other threads:[~2021-02-04 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 21:22 [Bug c/97882] New: " jarod.keene at trojans dot dsu.edu
2020-11-17 22:19 ` [Bug c/97882] [8/9/10/11 Regression] " jsm28 at gcc dot gnu.org
2020-11-18 15:29 ` jakub at gcc dot gnu.org
2021-01-14 9:41 ` rguenth at gcc dot gnu.org
2021-02-02 17:06 ` msebor at gcc dot gnu.org
2021-02-02 17:41 ` msebor at gcc dot gnu.org
2021-02-03 23:23 ` msebor at gcc dot gnu.org
2021-02-04 21:54 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-04 21:55 ` msebor at gcc dot gnu.org
2021-07-29 17:13 ` pinskia at gcc dot gnu.org
2021-07-29 17:16 ` pinskia 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-97882-4-Ydk7HjAgHO@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).