From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14514 invoked by alias); 23 Jun 2007 16:31:41 -0000 Received: (qmail 14505 invoked by uid 22791); 23 Jun 2007 16:31:36 -0000 X-Spam-Check-By: sourceware.org Received: from shell4.bayarea.net (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 23 Jun 2007 16:31:34 +0000 Received: (qmail 23699 invoked from network); 23 Jun 2007 09:31:32 -0700 Received: from 209-128-106-254.bayarea.net (HELO ?192.168.20.7?) (209.128.106.254) by shell4.bayarea.net with SMTP; 23 Jun 2007 09:31:32 -0700 Message-ID: <467D4AE3.7020505@eagercon.com> Date: Sat, 23 Jun 2007 16:31:00 -0000 From: Michael Eager User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Non-uniform address spaces Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00213.txt.bz2 Any suggestions on how to support a target which has a non-uniform address space? An address is a tuple which includes a processor id, a thread id, and an offset. There is a mapping function which translates the tuple into a physical address. Ideally, it would be nice to replace the current definition of CORE_ADDR with a struct and add functions to to do operations like increment/decrement address. But the assumption that the address space is flat and that you can do arithmetic on addresses is pervasive. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077