From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34540 invoked by alias); 3 Apr 2015 14:52:23 -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 34530 invoked by uid 89); 3 Apr 2015 14:52:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f175.google.com Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 03 Apr 2015 14:52:22 +0000 Received: by wibgn9 with SMTP id gn9so142312538wib.1 for ; Fri, 03 Apr 2015 07:52:19 -0700 (PDT) X-Received: by 10.194.157.68 with SMTP id wk4mr5376978wjb.130.1428072739213; Fri, 03 Apr 2015 07:52:19 -0700 (PDT) Received: from msticlxl7.ims.intel.com (jfdmzpr05-ext.jf.intel.com. [134.134.139.74]) by mx.google.com with ESMTPSA id lb6sm11820059wjb.22.2015.04.03.07.52.15 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Apr 2015 07:52:18 -0700 (PDT) Date: Fri, 03 Apr 2015 14:52:00 -0000 From: Ilya Tocar To: Uros Bizjak Cc: Kirill Yukhin , GCC Patches Subject: Re: [PATCH, i386] PR63211 broken type-punning in avx* tests. Message-ID: <20150403145207.GC23405@msticlxl7.ims.intel.com> References: <20150403110229.GB23405@msticlxl7.ims.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00124.txt.bz2 On 03 Apr 13:39, Uros Bizjak wrote: > On Fri, Apr 3, 2015 at 1:02 PM, Ilya Tocar wrote: > > > I've looked into avx* tests and many of them (even those that don't fail > > in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63211) use invalid type > > punning. Properly fixing them looks like a lot of work, so I propose > > just adding -fno-strict-aliasing to them. > > This patch was obtained by running > > sed -i "s/-O2/-O2 -fno-strict-aliasing/g" ../gcc/testsuite/gcc.target/i386/avx*-2.c > > > > Ok for stage1? > > I don't like this approach. If the testcase is broken, then it should > be fixed, not worked around. > IMHO those tests don't need to be alias conformant. There are plenty of tests for aliasing rules, and avx tests verify intrinsics implementaion. There are plenty of real programs braking alias rules, so why can't we have non-conformant tests?