From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id D9FB73858C2D for ; Thu, 23 Nov 2023 11:39:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D9FB73858C2D Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org D9FB73858C2D Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700739590; cv=none; b=jt4Y/cgxSelIgnm7O0uzr4vZxIo2Hy4NJhEe5klEvlmbKF0MkRD6Z0ZwdmWqkXey9Ntg7Co05+1+bLpxBjHl+cCH2lUg0zl8Xbr+WsRotkWrrkbN1pVGhr6TUAOFjP+Sd3oP5VM+WuMI2Gwo8IcIpf+L9tZUt4Gpy22QRU6IWtI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1700739590; c=relaxed/simple; bh=WOjQsv85WkvYbQ7hB79B+bul+hT4b7TPob5HGNFcNi0=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=xb4AM1rdsuRC4a2hFhhp9k6OqjKG/EvBkbt/pB0PwtwzF2sQhNI2nkY+/R5UcKmp/xo6FToyYm/85IHMqksdkl2GTvE0jVImMy/ItIV8E4AbsvRyfQKqlO4et/UyBeVISTi7d5EVjbsKFQhEWU4g/ev9NJ13bbTcmqWJVwloQMA= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1700739588; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dXYQ9m5ig6rVmizb2nfZFl39H2mSNXujfLdA53P9bWg=; b=AV/euJCEbi85mVW85hyRZIFKGm2WZwoiygvIeWtAhsvhUTq2UtCiHHx603jC/OJbSwzE5l kU7tQtiKmVLid5zkjfAudBEqSx0R84m8WMYYlcbqFUqxYSUmvEcGeBCw4e7s5Jzu8USel+ JG0DK0PoSOA+9kLy4cSxjUz+NO82p8A= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-231-8syWZlWrO4u608MqTqrE4Q-1; Thu, 23 Nov 2023 06:39:43 -0500 X-MC-Unique: 8syWZlWrO4u608MqTqrE4Q-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0039E101A52D; Thu, 23 Nov 2023 11:39:43 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.108]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 861D7C1596F; Thu, 23 Nov 2023 11:39:40 +0000 (UTC) From: Florian Weimer To: Tatsuyuki Ishi Cc: libc-alpha@sourceware.org, rui314@gmail.com, ruiu@bluewhale.systems, schwab@linux-m68k.org, adhemerval.zanella@linaro.org, andrew@sifive.com Subject: Re: [PATCH v4 3/3] RISC-V: Implement TLS Descriptors. References: <20230817181228.122674-2-ishitatsuyuki@gmail.com> <20230914084033.222120-1-ishitatsuyuki@gmail.com> <20230914084033.222120-4-ishitatsuyuki@gmail.com> Date: Thu, 23 Nov 2023 12:39:38 +0100 In-Reply-To: <20230914084033.222120-4-ishitatsuyuki@gmail.com> (Tatsuyuki Ishi's message of "Thu, 14 Sep 2023 17:40:33 +0900") Message-ID: <87ttpcd7gl.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,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: * Tatsuyuki Ishi: > + /* This is the slow path. We need to call __tls_get_addr() which > + means we need to save and restore all the register that the > + callee will trash. */ The ABI requires saving and restoring vector registers, too. The problem is that __tls_get_addr may end up calling a user-supplied malloc, and that might clobber vector registers. So it's not just dynamic loader code that is involved here, and we can't control how all relevant code is built. Thanks, Florian