From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id lDqxBmhvi2IE2wcAWB0awg (envelope-from ) for ; Mon, 23 May 2022 07:26:32 -0400 Received: by simark.ca (Postfix, from userid 112) id 0B7601E220; Mon, 23 May 2022 07:26:32 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=OlDV5LEp; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_DYNAMIC, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 908A31E01D for ; Mon, 23 May 2022 07:26:31 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 13930383A33F for ; Mon, 23 May 2022 11:26:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 13930383A33F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1653305191; bh=IjVIDRGwWWZAqMHLj+CUFNJEG2oAiYKW+2gXwBRs8z8=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=OlDV5LEpFzKPNNy1Hh/A2Fr+kcesXmBP9FgzjiuKQfSg2fh4YE4Z/ihUd2xxLHvV6 ABxa6RmfwtSoOPHHiFW1lbw9fFgYB+e1Pdo9GMzr4E8rM8lvQSfiG2cCMitHqLDq00 54s/0/sW92IlOvkjZus9sblAHSDpwsvy1IN6PopM= Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id 3AF103858010 for ; Mon, 23 May 2022 11:26:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3AF103858010 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 6A3761F8CF; Mon, 23 May 2022 11:26:11 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 432D1139F5; Mon, 23 May 2022 11:26:11 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 9kfsDlNvi2KpHgAAMHmgww (envelope-from ); Mon, 23 May 2022 11:26:11 +0000 Message-ID: Date: Mon, 23 May 2022 13:26:10 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH][gdb/testsuite] Fix printing of 0x10000000000000000 Content-Language: en-US To: Andrew Burgess , gdb-patches@sourceware.org References: <20220518122555.GA24256@delia> <87v8u1icjk.fsf@redhat.com> In-Reply-To: <87v8u1icjk.fsf@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Tom de Vries via Gdb-patches Reply-To: Tom de Vries Cc: Tom Tromey , Pedro Alves Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 5/19/22 20:48, Andrew Burgess wrote: > Maybe you're working on modula-2 right now, in which case, ignore this. > But, if you're not, then it might be better to raise a bug for the > module-2 issues - even if it's just "parse_number needs a rewrite", and > then use setup_xfail here instead of continue. > I filed: - https://sourceware.org/bugzilla/show_bug.cgi?id=29163 "[gdb/m2] parse_number needs rewrite" listing two UB errors. And then submitted this ( https://sourceware.org/pipermail/gdb-patches/2022-May/189313.html ) to fix those. > But otherwise, this all looks OK to me. Thanks for the review. I've now resubmitted in a slightly different format: - one patch to increase test coverage in gdb.base/parse_number.exp - patches for each language to address all exposes issues. I'm hoping that the per-language patches will be easier to review. Thanks, - Tom