From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by sourceware.org (Postfix) with ESMTPS id 8D1B13858401 for ; Thu, 1 Jun 2023 15:13:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8D1B13858401 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pl1-x62d.google.com with SMTP id d9443c01a7336-1b0236ee816so8151885ad.1 for ; Thu, 01 Jun 2023 08:13:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685632388; x=1688224388; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=jWkAROhMtszZKK/Px4QZ1ZWh9NHBGQKe65EUubeRPBs=; b=P/JDN3W97xIaFDtO+HCmxCbMrmuwCT7ERNeBbqyZXub2NbQL0zaSyBVMjfFno064r8 ojkQ1LLnWjxIMETZMTKti3aZDFiOKauTlHXMlLrKTBY10uKIw8GOxR8DJmPnpaPt9Mq4 mok8o4kD9629ASfcD5K2ypdCunfVBTdAhy5Mj60hICqxZHAQ2yCn9qspHTD7hL3gw3/3 Xw8cEywOCjYK0Jhzzkyt+MhvV+ZwHRUTQeCCOk639/4mk+ONULlY9SARezLumsehEi8d mbTAjhLDgJdqEWadW83zuWwIgpweudva5PNbpeUlzE9Cy6/FZZJDldFpuqQLfBSGQOIe 3jmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685632388; x=1688224388; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jWkAROhMtszZKK/Px4QZ1ZWh9NHBGQKe65EUubeRPBs=; b=eyMGvE1XqQhZ/Ud0/J4tbw2PK7bCe5cZVW9Lwl4rmgQ7A9eYY6rdEzP5USvuTMKz9o uMdg7m7Mf/y3cJjJBU4wMWCpWqDT3XJJlMvGYLMphWzbrzPyCI2T3VVUrKK9e8kJo1kD /FwYEBg2oXvGsaxl1T0sBM2jx+BV5RbUzHcsfZYJz+FYCMl945u83mSEaB4IX7XegPjT UXf6o1ou9dFA8etHaFLm6rGgYVwdTR793jGiOyQ/4f6CjmbCSMK0lChi0PieD67B3c7A t6R+7QFxbbqpn2FYG5ben9gYq6CIdKNEbRkSKppLxjM85NLxBezU5spiQKtAx1mPIXxe e2Qw== X-Gm-Message-State: AC+VfDwSlMwCKd3p4x+k0GTOmCjz1TRtpcrS0ERTLiLN1PG/7gux0zdP k9HrEgtwGsl6H3uXkH+nMccpId4z2mA= X-Google-Smtp-Source: ACHHUZ4D6iVPY9gXiovNpKnja2pSLucDQtD2+sPOALwEENGL7TyTyeFEn9+9zbuzEMB5xN2iON8uJA== X-Received: by 2002:a17:902:f68d:b0:1b1:91f1:a8b3 with SMTP id l13-20020a170902f68d00b001b191f1a8b3mr2820672plg.1.1685632388385; Thu, 01 Jun 2023 08:13:08 -0700 (PDT) Received: from ?IPV6:2601:681:8d00:265::f0a? ([2601:681:8d00:265::f0a]) by smtp.gmail.com with ESMTPSA id k10-20020a65464a000000b0052871962579sm3005683pgr.63.2023.06.01.08.13.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Jun 2023 08:13:07 -0700 (PDT) Message-ID: Date: Thu, 1 Jun 2023 09:13:06 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [PATCH v3] ifaddrs: Get rid of alloca Content-Language: en-US To: Florian Weimer , Jeff Law via Libc-alpha Cc: Joe Simmons-Talbott References: <20230530152539.2063770-1-josimmon@redhat.com> <855f0ed1-d05f-3b17-263b-a2957289e11d@gmail.com> <87ilc7rzn3.fsf@oldenburg.str.redhat.com> From: Jeff Law In-Reply-To: <87ilc7rzn3.fsf@oldenburg.str.redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 6/1/23 09:05, Florian Weimer wrote: > * Jeff Law via Libc-alpha: > >> Instead I wanted to have GCC prove particular allocations were safe to >> transform into alloca. That never panned out, but I still think the >> compiler is the right place to exploit the performance improvements >> one gets from alloca vs malloc/free. > > We got -fstack-clash-protection, which is I think is good enough from a > security point of view. Yea... Though I still want to dispose of explicitly using alloca :-) Interestingly enough I'm likey to have to spin up stack-clash-protection within the next few months for RISC-V. Though I may look to delegate it -- it'd be a great learning project for one of my compiler engineers. jeff