public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@golang.org>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
		"gofrontend-dev@googlegroups.com"
	<gofrontend-dev@googlegroups.com>
Subject: Go patch committed: Verify pointer's underlying type
Date: Tue, 04 Aug 2015 23:46:00 -0000	[thread overview]
Message-ID: <CAOyqgcXOdHf_gyGmfShmwLJrn0MuOTVqCfVL9qUeBn+0DSgxng@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 244 bytes --]

This patch from Chris Manghane ensures that when verifying a pointer
type, we verify the underlying type.  This fixes
https://golang.org/issue/11547 .  Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu.  Committed to mainline.

Ian

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 805 bytes --]

Index: gcc/go/gofrontend/MERGE
===================================================================
--- gcc/go/gofrontend/MERGE	(revision 226596)
+++ gcc/go/gofrontend/MERGE	(working copy)
@@ -1,4 +1,4 @@
-df080adb06f0e423820f3f6b9604b0c1093ff20a
+6fb7c3509a4eda7d2403900981b53029d6727037
 
 The first line of this file holds the git revision number of the last
 merge done from the gofrontend repository.
Index: gcc/go/gofrontend/types.h
===================================================================
--- gcc/go/gofrontend/types.h	(revision 226510)
+++ gcc/go/gofrontend/types.h	(working copy)
@@ -2033,6 +2033,10 @@ class Pointer_type : public Type
   do_traverse(Traverse*);
 
   bool
+  do_verify()
+  { return this->to_type_->verify(); }
+
+  bool
   do_has_pointer() const
   { return true; }
 

                 reply	other threads:[~2015-08-04 23:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAOyqgcXOdHf_gyGmfShmwLJrn0MuOTVqCfVL9qUeBn+0DSgxng@mail.gmail.com \
    --to=iant@golang.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.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).