public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] Add comments to check-c++-types.sh
Date: Thu, 08 Dec 2016 16:27:00 -0000	[thread overview]
Message-ID: <201612081627.uB8GRTxO016049@sellcey-lt.caveonetworks.com> (raw)

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 |

             reply	other threads:[~2016-12-08 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 16:27 Steve Ellcey [this message]
2016-12-27 22:21 ` Steve Ellcey

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=201612081627.uB8GRTxO016049@sellcey-lt.caveonetworks.com \
    --to=sellcey@cavium.com \
    --cc=libc-alpha@sourceware.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).