From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66046 invoked by alias); 4 May 2018 17:27:17 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 66030 invoked by uid 89); 4 May 2018 17:27:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 04 May 2018 17:27:15 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 66C497D83F; Fri, 4 May 2018 17:27:14 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id E81562166BAD; Fri, 4 May 2018 17:27:13 +0000 (UTC) Subject: Re: [PATCH 28/40] target_ops/C++: SPU/Linux To: Ulrich Weigand References: <20180504172214.CF910D804F4@oc3748833570.ibm.com> Cc: gdb-patches@sourceware.org From: Pedro Alves Message-ID: Date: Fri, 04 May 2018 17:27:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180504172214.CF910D804F4@oc3748833570.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-05/txt/msg00108.txt.bz2 On 05/04/2018 06:22 PM, Ulrich Weigand wrote: > Pedro Alves wrote: >> On 05/04/2018 06:08 PM, Ulrich Weigand wrote: >>> Hi Pedro, >>> >>>> +ptid_t >>>> +spu_linux_nat_target:::wait (ptid_t ptid, struct target_waitstatus *ourstatus, >>>> + int options) >>> >>> This syntax error (:::) causes a build break on SPU. >> Sorry about that. Are you able to push in the obvious fix, >> or would you rather me do it? > > No problem :-) I've checked the fix in now. Thanks you. :-) Pedro Alves