From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7503 invoked by alias); 21 Jan 2015 15:07:15 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 7452 invoked by uid 89); 21 Jan 2015 15:07:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qa0-f51.google.com Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com) (209.85.216.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 21 Jan 2015 15:07:06 +0000 Received: by mail-qa0-f51.google.com with SMTP id f12so32511211qad.10 for ; Wed, 21 Jan 2015 07:07:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DIj/xIunEAGmaY0LVqc6YIxc6jR2HA0LsVrYahzvwoI=; b=jyQh3acja8+s2lsjwe7mO1MAs0KySdu+BKaPHmJh9a39SYAvOowby8PLhUAYOB3v1o lq5qn+BwQumXThyuWdVoFJYKoNvUAG+OZIxTV3vKcVNhhG+KOv0LUqFzKWqRSTOy3sBW raTnwU2334FkjcZUyGLLwJc+RN5wahXg5RtG2X1ecNMPiI/hM2X6S5h/m6Y3HKqv2Bwl FnrTBXmmARm+o5Zju4H2NbvV4jSmbWR7sku9VoczSROHdDIrcVnbrT2AnL/5Qo66iPWv BgG4aYbpF69Y8mFFntw/VmufvQKgpg8WNTsl+lUTgXC6DjZqUH1ak/3IirB6cAmOaRY5 CGKg== X-Gm-Message-State: ALoCoQlvbAIUxH6PIlmnMQeDRISmSJuF8Enb7ZUYdC3bfDhsOoZuhdQVfTqKHGlBO5YNFgW/3+kx MIME-Version: 1.0 X-Received: by 10.229.172.196 with SMTP id m4mr22489941qcz.19.1421852824171; Wed, 21 Jan 2015 07:07:04 -0800 (PST) Received: by 10.140.84.176 with HTTP; Wed, 21 Jan 2015 07:07:04 -0800 (PST) In-Reply-To: References: <1421162314-25779-1-git-send-email-christophe.lyon@linaro.org> <1421162314-25779-4-git-send-email-christophe.lyon@linaro.org> <54B9187A.7000406@arm.com> Date: Wed, 21 Jan 2015 16:35:00 -0000 Message-ID: Subject: Re: [[ARM/AArch64][testsuite] 03/36] Add vmax, vmin, vhadd, vhsub and vrhadd tests. From: Christophe Lyon To: Marcus Shawcroft Cc: "gcc-patches@gcc.gnu.org" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg01918.txt.bz2 On 19 January 2015 at 17:54, Marcus Shawcroft wrote: > On 19 January 2015 at 15:43, Christophe Lyon wrote: >> On 19 January 2015 at 14:29, Marcus Shawcroft >> wrote: >>> On 16 January 2015 at 17:52, Christophe Lyon wrote: >>> >>>>> OK provided, as per the previous couple, that we don;t regression or >>>>> introduce new fails on aarch64[_be] or aarch32. >>>> >>>> This patch shows failures on aarch64 and aarch64_be for vmax and vmin >>>> when the input is -NaN. >>>> It's a corner case, and my reading of the ARM ARM is that the result >>>> should the same as on aarch32. >>>> I haven't had time to look at it in more details though. >>>> So, not OK? >>> >>> They should have the same behaviour in aarch32 and aarch64. Did you >>> test on HW or a model? >>> >> I ran the tests on qemu for aarch32 and aarch64-linux, and on the >> foundation model for aarch64*-elf. > > Leave this one out until we understand why it fails. /Marcus I've looked at this a bit more. We have fmax v0.4s, v0.4s, v1.4s where v0 is a vector of -NaN (0xffc00000) and v1 is a vector of 1. The output is still -NaN (0xffc00000), while the test expects defaultNaN (0x7fc00000). I have executed the test under GDB on AArch64 HW, and noticed that fpcr was 0. I forced it to have DN==1: set $fpcr=0x1000000 but this didn't change the result. Does setting fpcr.dn under gdb actually work? Christophe.