From 9410e125dab367e7eb002fbf68fd38680f1d436e Mon Sep 17 00:00:00 2001
From: Daniel Kirchner <daniel@ekpyron.org>
Date: Mon, 14 Mar 2022 11:54:09 +0100
Subject: [PATCH] Change memory-safe assembly annotation suggestion during
 stack too deep errors.

---
 libyul/backends/evm/EVMObjectCompiler.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libyul/backends/evm/EVMObjectCompiler.cpp b/libyul/backends/evm/EVMObjectCompiler.cpp
index b60e383e6..4dbf5cc1a 100644
--- a/libyul/backends/evm/EVMObjectCompiler.cpp
+++ b/libyul/backends/evm/EVMObjectCompiler.cpp
@@ -89,7 +89,7 @@ void EVMObjectCompiler::run(Object& _object, bool _optimize)
 			if (memoryGuardCalls.empty())
 				msg += "\nNo memoryguard was present. "
 					"Consider using memory-safe assembly only and annotating it via "
-					"\"/// @solidity memory-safe-assembly\".";
+					"'assembly (\"memory-safe\") { ... }'.";
 			else
 				msg += "\nmemoryguard was present.";
 			stackError << util::errinfo_comment(msg);