From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83513 invoked by alias); 23 Feb 2019 01:56:57 -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 82902 invoked by uid 89); 23 Feb 2019 01:56:52 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 23 Feb 2019 01:56:51 +0000 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D0BE8307EA96; Sat, 23 Feb 2019 01:56:49 +0000 (UTC) Received: from localhost (ovpn-116-60.phx2.redhat.com [10.3.116.60]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7AC925D9CA; Sat, 23 Feb 2019 01:56:49 +0000 (UTC) Date: Sat, 23 Feb 2019 02:26:00 -0000 From: Jonathan Wakely To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: [PATCH] PR libstdc++/89446 fix null pointer dereference in char_traits Message-ID: <20190223015649.GT13569@redhat.com> References: <20190223010220.GA32714@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190223010220.GA32714@redhat.com> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.10.1 (2018-07-13) X-SW-Source: 2019-02/txt/msg01875.txt.bz2 On 23/02/19 01:02 +0000, Jonathan Wakely wrote: >+// { dg-options "-std=gnu++17 -fexceptions -fnon-call-exceptions -O1" } >+// { dg-do run { target { powerpc*-*-linux* i?86-*-linux* x86_64-*-linux* } } } I forgot to say that this is a conservative list of targets where -fnon-call-exceptions is supported. Maybe it could run on other targets, but this should be enough to ensure we don't get a regression for this bug.