From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32103 invoked by alias); 24 Jun 2014 16:16:47 -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 32092 invoked by uid 89); 24 Jun 2014 16:16:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-vc0-f173.google.com Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 24 Jun 2014 16:16:44 +0000 Received: by mail-vc0-f173.google.com with SMTP id lf12so566380vcb.18 for ; Tue, 24 Jun 2014 09:16:42 -0700 (PDT) X-Received: by 10.220.174.137 with SMTP id t9mr1693412vcz.12.1403626602490; Tue, 24 Jun 2014 09:16:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.30.227 with HTTP; Tue, 24 Jun 2014 09:16:22 -0700 (PDT) In-Reply-To: <53A99C6D.2030001@verizon.net> References: <53A96A06.7050304@verizon.net> <53A999B0.5050704@verizon.net> <53A99C6D.2030001@verizon.net> From: Andrew Sutton Date: Tue, 24 Jun 2014 16:16:00 -0000 Message-ID: Subject: Re: [c++-concepts] Fix assertion failure with cp_maybe_constrained_type_specifier To: Ed Smith-Rowland <3dw4rd@verizon.net> Cc: gcc-patches , Braden Obrzut Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2014-06/txt/msg01914.txt.bz2 Weird. Any chance you're doing a bootstrap build? There was an earlier bootstrapping issue with this branch. We had turned on -std=c++1y by default, and it was causing some conversion errors with lvalue references to bitfields in libasan. This doesn't *look* like a regression caused by concepts -- I don't think I'm touching the initializer code at all. Andrew Sutton On Tue, Jun 24, 2014 at 11:42 AM, Ed Smith-Rowland <3dw4rd@verizon.net> wrote: > I'm not sure the warning is correct in any case... > > In i386.h > ------------ > struct stringop_algs > { > const enum stringop_alg unknown_size; > const struct stringop_strategy { > const int max; > const enum stringop_alg alg; > int noalign; > } size [MAX_STRINGOP_ALGS]; > }; > > in i386.c > ----------- > static stringop_algs ix86_size_memcpy[2] = { > {rep_prefix_1_byte, {{-1, rep_prefix_1_byte, false}}}, > {rep_prefix_1_byte, {{-1, rep_prefix_1_byte, false}}}}; > static stringop_algs ix86_size_memset[2] = { > {rep_prefix_1_byte, {{-1, rep_prefix_1_byte, false}}}, > {rep_prefix_1_byte, {{-1, rep_prefix_1_byte, false}}}}; >