From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,NICE_REPLY_A,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6510 invoked from network); 10 Nov 2020 08:21:08 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 10 Nov 2020 08:21:08 -0000 Received: (qmail 17913 invoked by uid 550); 10 Nov 2020 08:21:06 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17894 invoked from network); 10 Nov 2020 08:21:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604996454; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nKgE+086RQwNWD/0hFBQGgJH765Mrxqsw6jm1qFKQWs=; b=Q5/czYgunMbIcGa8IEeNdQKcj85i8kflTIlPlLPHQKd2zxFUxya5vIYDuDz+1RJ1hT641n KkqkG+SQp0CsJ0i33uNGByPNvtgf3IyW3qTW8wkXFYKRdV6dHe+UjPRaVmetoj3YyPRNrv 3eG4vp6uAtKwj7+G6j/Xa90jEryjOZQ= X-MC-Unique: 6ghTsN4UOzu0HXxuTcaIYw-1 To: musl@lists.openwall.com References: From: Harald Hoyer Message-ID: <1e5bc463-e1a6-f9b4-8b3c-020eb535f946@redhat.com> Date: Tue, 10 Nov 2020 09:20:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=harald@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [musl] x86_64/__set_thread_area clobber of rcx and r11 Am 09.11.20 um 22:59 schrieb Hydro Flask: > On 2020-11-09 13:48, Harald Hoyer wrote: >> In src/thread/x86_64/__set_thread_area.s, I don't see any special >> handling of the registers rcx and r11, >> which will be clobbered by the syscall. Is that an oversight, or am I >> missing something? > > The x86_64 ABI states that code should assume all caller-saved registers, which include rcx and r11, are clobbered > after the function call. __set_thread_area itself doesn't use rcx or r11, so no other special handling is needed. > Yeah, sorry, memorized half an hour later also. I guess it was too much inline assembly in the last weeks.