From: "Arsen Arsenović" <arsen@aarsen.me>
To: gcc-patches@gcc.gnu.org
Cc: jason@redhat.com, jchapman@lock3software.com,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: [PATCH] contracts: Stop relying on mangling for naming .pre/.post clones
Date: Sat, 10 Dec 2022 14:13:56 +0100 [thread overview]
Message-ID: <20221210131356.3385654-1-arsen@aarsen.me> (raw)
If the mangler is relied on, functions with extern "C" on them emit multiple
definitions of the same name.
gcc/cp/ChangeLog:
* contracts.cc (build_contract_condition_function): Add pre/post
suffixes to pre- and postcondition clones.
* mangle.cc (write_encoding): Don't mangle pre- and postconditions.
gcc/testsuite/ChangeLog:
* g++.dg/contracts/contracts-externC.C: New test.
---
Afternoon,
This change prevents contracts from emitting wrapper functions that have the
same name as the original function, by moving the logic that disambiguates them
from the mangler into the build_contract_condition_function helper.
Thanks, have nice day.
gcc/cp/contracts.cc | 3 +++
gcc/cp/mangle.cc | 7 -------
.../g++.dg/contracts/contracts-externC.C | 19 +++++++++++++++++++
3 files changed, 22 insertions(+), 7 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/contracts/contracts-externC.C
diff --git a/gcc/cp/contracts.cc b/gcc/cp/contracts.cc
index 26316372389..f09eb87e283 100644
--- a/gcc/cp/contracts.cc
+++ b/gcc/cp/contracts.cc
@@ -161,6 +161,7 @@ along with GCC; see the file COPYING3. If not see
#include "tree-iterator.h"
#include "print-tree.h"
#include "stor-layout.h"
+#include "cgraph.h"
const int max_custom_roles = 32;
static contract_role contract_build_roles[max_custom_roles] = {
@@ -1451,6 +1452,8 @@ build_contract_condition_function (tree fndecl, bool pre)
TREE_TYPE (fn) = build_method_type (class_type, TREE_TYPE (fn));
DECL_NAME (fn) = copy_node (DECL_NAME (fn));
+ auto suffix = pre ? "pre" : "post";
+ SET_DECL_ASSEMBLER_NAME (fn, clone_function_name (fn, suffix));
DECL_INITIAL (fn) = error_mark_node;
DECL_ABSTRACT_ORIGIN (fn) = fndecl;
diff --git a/gcc/cp/mangle.cc b/gcc/cp/mangle.cc
index e363ef35b9f..e97428e8f30 100644
--- a/gcc/cp/mangle.cc
+++ b/gcc/cp/mangle.cc
@@ -856,13 +856,6 @@ write_encoding (const tree decl)
mangle_return_type_p (decl),
d);
- /* If this is the pre/post function for a guarded function, append
- .pre/post, like something from create_virtual_clone. */
- if (DECL_IS_PRE_FN_P (decl))
- write_string (".pre");
- else if (DECL_IS_POST_FN_P (decl))
- write_string (".post");
-
/* If this is a coroutine helper, then append an appropriate string to
identify which. */
if (tree ramp = DECL_RAMP_FN (decl))
diff --git a/gcc/testsuite/g++.dg/contracts/contracts-externC.C b/gcc/testsuite/g++.dg/contracts/contracts-externC.C
new file mode 100644
index 00000000000..873056b742b
--- /dev/null
+++ b/gcc/testsuite/g++.dg/contracts/contracts-externC.C
@@ -0,0 +1,19 @@
+// simple check to ensure we don't emit a function with the same name twice,
+// when wrapping functions in pre- and postconditions.
+// { dg-do link }
+// { dg-options "-std=c++2a -fcontracts -fcontract-continuation-mode=on" }
+
+volatile int x = 10;
+
+extern "C" void
+f ()
+ [[ pre: x < 10 ]]
+{
+}
+
+int
+main ()
+ [[ post: x > 10 ]]
+{
+ f();
+}
--
2.38.1
next reply other threads:[~2022-12-10 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 13:13 Arsen Arsenović [this message]
2022-12-10 13:14 ` Arsen Arsenović
2022-12-10 19:51 ` Bernhard Reutner-Fischer
2022-12-11 15:56 ` Arsen Arsenović
2022-12-15 15:40 ` Jason Merrill
2022-12-15 18:00 ` Arsen Arsenović
2022-12-15 20:29 ` Iain Sandoe
2022-12-17 11:30 ` Arsen Arsenović
2022-12-15 21:48 ` Jason Merrill
2022-12-17 11:30 ` Arsen Arsenović
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=20221210131356.3385654-1-arsen@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jchapman@lock3software.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).