From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1137 invoked by alias); 10 Jun 2005 20:23:52 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1081 invoked by uid 22791); 10 Jun 2005 20:23:43 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 10 Jun 2005 20:23:43 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j5AKNfDr012288 for ; Fri, 10 Jun 2005 16:23:41 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5AKNdO10979; Fri, 10 Jun 2005 16:23:39 -0400 Received: from [172.16.24.50] (bluegiant.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id j5AKNPZF000540; Fri, 10 Jun 2005 16:23:28 -0400 Message-ID: <42A9F6B6.5090307@redhat.com> Date: Fri, 10 Jun 2005 20:23:00 -0000 From: Michael Snyder User-Agent: Mozilla Thunderbird (X11/20050322) MIME-Version: 1.0 To: Andreas Schwab CC: Jason Molenda , gdb-patches@sources.redhat.com Subject: Re: The gdb x86 function prologue parser References: <85C775AE-3B05-431E-96D2-49EA9D1413E6@apple.com> <20050608232556.A53178@molenda.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg00096.txt.bz2 Andreas Schwab wrote: > Jason Molenda writes: > > >>Hi Andreas, >> >>On Wed, Jun 08, 2005 at 09:58:12PM +0200, Andreas Schwab wrote: >> >> >>>>>+#include >>> >>>Since this is a target (not native) file it needs to use types portable to >>>all hosts. >> >>I'll drop stdint.h because it requires ISO C99, but I don't understand >>your comment. Is there some environment where uint32_t isn't 4 bytes? > > > If uint32_t is available at all, you can't universally assume that. I was > referring to the statement from Eli, who said "replaceable by suitable > standard x86 types", but this file must be compilable on any host, not > only x86. Yes, you just have to make sure that the "standard x86 types" are used only for target-side data objects, not host-side ones.