public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: putting Ptrace back to 64-bit
Date: Thu, 02 Aug 2007 12:37:00 -0000	[thread overview]
Message-ID: <46B1D016.909@redhat.com> (raw)
In-Reply-To: <1186043998.15044.47.camel@dijkstra.wildebeest.org>

Mark Wielaard wrote:
> Hi Andrew,
>
> On Wed, 2007-08-01 at 22:58 -0400, Andrew Cagney wrote:
>   
>> I don't understand the rationale behind this change:
>>     
>
> It was proposed and explained as a follow up for the LogicalMemoryBuffer
> under "A couple of things to note, questions and upcoming work" at:
> http://sourceware.org/ml/frysk/2007-q3/msg00163.html
> And the rationale was again added when the actual patch to implement it
> was posted: http://sourceware.org/ml/frysk/2007-q3/msg00216.html
>   

Please run such things directly past me.
>   
>> It forces calling code to contend with Java's bone-head "int" is 32-bits 
>> and be damed.
>>     
>
>   
That is Java's 32-bit bonehead ism.  This exports a 64-bit interface; 
we'll keep it that way.



> No, the patch carefully only changes those calls that take a 32-bit
> (actually positive "int" byte[]) container in the first place so that
> the calling code is consistent and calls to these methods get flagged at
> compile time if they provide inconsistent arguments. None of the
> arguments that actually are 64-bit were changed of course.
>
> Cheers,
>
> Mark
>   

  reply	other threads:[~2007-08-02 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  2:58 Andrew Cagney
2007-08-02  8:40 ` Mark Wielaard
2007-08-02 12:37   ` Andrew Cagney [this message]
2007-08-02 14:00     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B1D016.909@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).