From patchwork Tue Mar 1 23:41:56 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "H.J. Lu" X-Patchwork-Id: 11164 Received: (qmail 85556 invoked by alias); 1 Mar 2016 23:41:58 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Delivered-To: mailing list libc-alpha@sourceware.org Received: (qmail 85539 invoked by uid 89); 1 Mar 2016 23:41:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00, KAM_LAZY_DOMAIN_SECURITY, NO_DNS_FOR_FROM, RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*F:U*hjl X-HELO: mga09.intel.com X-ExtLoop1: 1 Date: Tue, 1 Mar 2016 15:41:56 -0800 From: "H.J. Lu" To: GNU C Library Subject: PATCH: Call x86-64 __setcontext directly Message-ID: <20160301234155.GA16092@intel.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Since x86-64 __start_context calls the internal __setcontext, it should call __setcontext directly. I will check it in shortly. H.J. --- * sysdeps/unix/sysv/linux/x86_64/__start_context.S (__start_context): Call __setcontext directly. diff --git a/sysdeps/unix/sysv/linux/x86_64/__start_context.S b/sysdeps/unix/sysv/linux/x86_64/__start_context.S index 408d30d..6a33cd0 100644 --- a/sysdeps/unix/sysv/linux/x86_64/__start_context.S +++ b/sysdeps/unix/sysv/linux/x86_64/__start_context.S @@ -36,7 +36,7 @@ ENTRY(__start_context) testq %rdi, %rdi je 2f /* If it is zero exit. */ - call JUMPTARGET(__setcontext) + call __setcontext /* If this returns (which can happen if the syscall fails) we'll exit the program with the return error value (-1). */ movq %rax,%rdi