Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Address FIXME in i386-tdep.c:i386_extract_struct_value_address
Date: Sun, 27 Oct 2002 08:25:00 -0000	[thread overview]
Message-ID: <200210271625.g9RGP9ks005560@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3DBACF7C.4010403@redhat.com> (message from Andrew Cagney on Sat, 26 Oct 2002 13:23:08 -0400)

   Date: Sat, 26 Oct 2002 13:23:08 -0400
   From: Andrew Cagney <ac131313@redhat.com>

   > We know for sure here that we're not dealing with a cooked register.

   That's what you think :-)  It's more correct here to use the cooked 
   interface.

Care to enlighten me?  Is it that one should always use the cooked
interface, except in code that's present to support the cooked
interface in the first place?

Mark


  reply	other threads:[~2002-10-27 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26  7:41 Mark Kettenis
2002-10-26 10:23 ` Andrew Cagney
2002-10-27  8:25   ` Mark Kettenis [this message]
2002-11-07 15:12     ` Andrew Cagney

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=200210271625.g9RGP9ks005560@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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