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 <gofrontend-dev@googlegroups.com>
Subject: Go patch committed: Remove range-based for loop
Date: Thu, 30 May 2019 03:49:00 -0000	[thread overview]
Message-ID: <CAOyqgcUDXtSm9t_Pu7+qGQGoud+EPqOxdp9Wkw-qaJh98Bw1-w@mail.gmail.com> (raw)

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

The Go frontend is currently supposed to use C++98.  This patch by
Than McIntosh removes a range based for loop that snuck in recently.
This fixes PR 90669.  Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu.  Committed to mainline.

Ian

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

Index: gcc/go/gofrontend/MERGE
===================================================================
--- gcc/go/gofrontend/MERGE	(revision 271669)
+++ gcc/go/gofrontend/MERGE	(working copy)
@@ -1,4 +1,4 @@
-3995d545f1e112c682753f342eaef0877551a649
+84b8000c32f671c6cc89df1290ed6e0170308644
 
 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.cc
===================================================================
--- gcc/go/gofrontend/types.cc	(revision 271669)
+++ gcc/go/gofrontend/types.cc	(working copy)
@@ -2802,8 +2802,13 @@ Ptrmask::symname() const
 
       // Redirect the bits vector to the digest, and update the prefix.
       prefix = "X";
-      for (char c : digest)
-        shabits.push_back((unsigned char) c);
+      for (std::string::const_iterator p = digest.begin();
+           p != digest.end();
+           ++p)
+        {
+          unsigned char c = *p;
+          shabits.push_back(c);
+        }
       bits = &shabits;
     }
 

                 reply	other threads:[~2019-05-30  0:57 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=CAOyqgcUDXtSm9t_Pu7+qGQGoud+EPqOxdp9Wkw-qaJh98Bw1-w@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).