From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-433361-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 19959 invoked by alias); 5 Aug 2016 18:16:10 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 19485 invoked by uid 89); 5 Aug 2016 18:16:10 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=
X-HELO: mailout05.t-online.de
Received: from mailout05.t-online.de (HELO mailout05.t-online.de) (194.25.134.82) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 05 Aug 2016 18:16:08 +0000
Received: from fwd00.aul.t-online.de (fwd00.aul.t-online.de [172.20.26.147])	by mailout05.t-online.de (Postfix) with SMTP id 22537423A494;	Fri,  5 Aug 2016 20:16:04 +0200 (CEST)
Received: from [192.168.0.16] (VyKbpuZBghujUKFLxr4wYaAl2SULqKmuNIHLE4Z0O2eBwUiqyWmRSkjx5QCyzmFQ-W@[115.165.93.200]) by fwd00.t-online.de	with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted)	esmtp id 1bVjf4-19Luoy0; Fri, 5 Aug 2016 20:15:58 +0200
Message-ID: <1470420954.639.64.camel@t-online.de>
Subject: Re: protected alloca class for malloc fallback
From: Oleg Endo <oleg.endo@t-online.de>
To: Richard Biener <richard.guenther@gmail.com>, Aldy Hernandez	 <aldyh@redhat.com>, Martin Sebor <msebor@gmail.com>, gcc-patches	 <gcc-patches@gcc.gnu.org>
Date: Fri, 05 Aug 2016 18:16:00 -0000
In-Reply-To: <A04768E7-68E6-4331-B5C4-1C28003BF383@gmail.com>
References: <57A32741.7010003@redhat.com> <57A3F57F.3050509@gmail.com>	 <57A4A5E8.90205@redhat.com>	 <A04768E7-68E6-4331-B5C4-1C28003BF383@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
X-SW-Source: 2016-08/txt/msg00486.txt.bz2

On Fri, 2016-08-05 at 19:55 +0200, Richard Biener wrote:

> 
> Please don't use std::string.  For string building you can use
> obstacks.
> 

Just out of curiosity ... why?  I remember there was some discussion
about it, what was the conclusion?  Is that now a general rule or does
it depend on the context where strings are used?

Cheers,
Oleg