From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14670 invoked by alias); 4 Oct 2003 04:54:11 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14654 invoked from network); 4 Oct 2003 04:54:10 -0000 Received: from unknown (HELO cs20.apochromatic.org) (204.152.189.161) by sources.redhat.com with SMTP; 4 Oct 2003 04:54:10 -0000 Received: from i8k.3am-software.com (localhost [127.0.0.1]) by cs20.apochromatic.org (Postfix) with ESMTP id 82B4E17E81 for ; Fri, 3 Oct 2003 21:53:08 -0700 (PDT) Message-Id: <6.0.0.22.2.20031003213940.035e26d0@3am-software.com> X-Sender: matt@3am-software.com Date: Sat, 04 Oct 2003 04:54:00 -0000 To: gcc@gcc.gnu.org From: Matt Thomas Subject: PA-RISC: Reserving a "thread context" register. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2003-10/txt/msg00128.txt.bz2 As NetBSD is finishing off work on a toolchain for hppa platform using the Linux ELF PA-RISC support as a base, someone suggested that it might be worth reserving a register for a thread context. If we did so, what would be the best register to use? Is there a better method to do what we want? -- Matt Thomas email: matt@3am-software.com 3am Software Foundry www: http://3am-software.com/bio/matt/ Cupertino, CA disclaimer: I avow all knowledge of this message.