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/111708] Calling external global function instead of local static function. Date: Tue, 17 Oct 2023 18:19:35 +0000 [thread overview] Message-ID: <bug-111708-4-oTulAivyYc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111708-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111708 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Uecker <uecker@gcc.gnu.org>: https://gcc.gnu.org/g:1f186f64b8602d74769af4a6250255e51227f744 commit r14-4689-g1f186f64b8602d74769af4a6250255e51227f744 Author: Martin Uecker <uecker@tugraz.at> Date: Sat Oct 14 09:09:07 2023 +0200 c: error for function with external and internal linkage [PR111708] Declaring a function with both external and internal linkage in the same TU is translation-time UB. Add an error for this case as already done for objects. PR c/111708 gcc/c/ChangeLog: * c-decl.cc (grokdeclarator): Add error. gcc/testsuite/ChangeLog: * gcc.dg/pr111708-1.c: New test. * gcc.dg/pr111708-2.c: New test.
next prev parent reply other threads:[~2023-10-17 18:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-05 17:47 [Bug c/111708] New: " k.frolov at samsung dot com 2023-10-05 18:08 ` [Bug c/111708] " pinskia at gcc dot gnu.org 2023-10-05 18:12 ` pinskia at gcc dot gnu.org 2023-10-06 11:56 ` k.frolov at samsung dot com 2023-10-06 12:14 ` k.frolov at samsung dot com 2023-10-06 12:32 ` k.frolov at samsung dot com 2023-10-08 8:36 ` muecker at gwdg dot de 2023-10-08 18:19 ` muecker at gwdg dot de 2023-10-14 12:43 ` muecker at gwdg dot de 2023-10-17 18:19 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-03 19:14 ` uecker at gcc dot gnu.org 2023-12-17 20:51 ` 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-111708-4-oTulAivyYc@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: linkBe 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).