From patchwork Thu Dec  8 16:27:29 2016
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Steve Ellcey <sellcey@cavium.com>
X-Patchwork-Id: 18293
Received: (qmail 28878 invoked by alias); 8 Dec 2016 16:27:43 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Unsubscribe: <mailto:libc-alpha-unsubscribe-##L=##H@sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>,
	<http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Delivered-To: mailing list libc-alpha@sourceware.org
Received: (qmail 26933 invoked by uid 89); 8 Dec 2016 16:27:42 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.9 required=5.0 tests=AWL, BAYES_00,
	KAM_LAZY_DOMAIN_SECURITY,
	RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=
X-HELO: camailhost.cavium.com
Date: Thu, 8 Dec 2016 08:27:29 -0800
From: Steve Ellcey <sellcey@cavium.com>
Message-Id: <201612081627.uB8GRTxO016049@sellcey-lt.caveonetworks.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] Add comments to check-c++-types.sh
Reply-To: sellcey@cavium.com

I would like to add some comments to scripts/check-c++-types.sh to make
it more obvious what it is doing.  Does this text look OK?

Steve Ellcey
sellcey@caviumnetworks.com


2016-12-08  Steve Ellcey  <sellcey@caviumnetworks.com>

	* scripts/check-c++-types.sh: Add comments.

diff --git a/scripts/check-c++-types.sh b/scripts/check-c++-types.sh
index 489c4f0..f82ffff 100755
--- a/scripts/check-c++-types.sh
+++ b/scripts/check-c++-types.sh
@@ -15,6 +15,14 @@
 # You should have received a copy of the GNU Lesser General Public
 # License along with the GNU C Library; if not, see
 # <http://www.gnu.org/licenses/>.
+
+# This script creates a list of data types where each type is followed
+# by the C++ mangled name for that type.  That list is then compared
+# against the list in the c++-types.data file for the platform being
+# checked.  Any difference between the two would mean that the C++ ABI
+# had changed and that should not happen even if the change is compatible
+# at the C language level.
+
 #
 # The list of data types has been created with
 # cat <<EOF |