From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 6FA293890421 for ; Thu, 2 Jul 2020 20:52:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6FA293890421 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [10.0.0.11] (173-246-6-90.qc.cable.ebox.net [173.246.6.90]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id F0B271E5F9; Thu, 2 Jul 2020 16:52:45 -0400 (EDT) Subject: Re: [PATCH] Skip tests requiring "alignof (void)" when compiling using clang To: Pedro Alves , Gary Benson , gdb-patches@sourceware.org References: <1593529380-8689-1-git-send-email-gbenson@redhat.com> From: Simon Marchi Message-ID: <8361fbe3-9843-95c1-6451-7a1a2aa0463e@simark.ca> Date: Thu, 2 Jul 2020 16:52:45 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: fr Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org 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: , X-List-Received-Date: Thu, 02 Jul 2020 20:52:47 -0000 On 2020-07-02 4:49 p.m., Pedro Alves wrote: > I think this should still test GDB's support. And a > comment would be helpful. Like: > > # As an extension, GCC allows void pointer arithmetic, with > # sizeof(void) and alignof(void) both 1. GDB supports GCC's > # extension. Clang does not. > if ![test_compiler_info clang*] { > set expected [get_integer_valueof a_void 0] > gdb_test "print alignof(void)" " = $expected" > } else { > gdb_test "print alignof(void)" " = 1" > } Indeed. Otherwise, let's say that clang gain this feature, it would remain untested (when testing with clang) and nobody would think of coming here to update the test case. Here, if clang gains the feature, then I suppose it would generate a FAIL, which would prompt us to update the test case. Simon