Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vladimir@codesourcery.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [m68k] correct m68k_convert_register_p for coldfire
Date: Fri, 06 Nov 2009 23:27:00 -0000	[thread overview]
Message-ID: <200911062325.nA6NPZHv008499@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <hd1m4u$5lg$1@ger.gmane.org> (message from Vladimir Prus on Fri, 	06 Nov 2009 20:24:47 +0300)

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date:  Fri, 06 Nov 2009 20:24:47 +0300
> > Please don't apply this as is without at least trying to
> > build it...  current_gdbarch doesn't exist anymore.
> 
> Doh! Here's what I've ended up checking it.

But that doesn't make any sense.  On a real m68k,
register_type(gdbarch, M68K_FP0_REGNUM) will return
m68881_ext_type(gdbarch) and on coldfire, type !=
m68881_ext_type(gdbarch) is probably always true.

> Index: gdb/ChangeLog
> ===================================================================
> RCS file: /cvs/src/src/gdb/ChangeLog,v
> retrieving revision 1.11036
> diff -u -p -r1.11036 ChangeLog
> --- gdb/ChangeLog	6 Nov 2009 14:26:09 -0000	1.11036
> +++ gdb/ChangeLog	6 Nov 2009 17:21:57 -0000
> @@ -1,5 +1,11 @@
>  2009-11-06  Vladimir Prus  <vladimir@codesourcery.com>
>  
> +	* m68k-tdep.c (m68k_convert_register_p): Compare with
> +	the actual type of fp registers, not one of the possible
> +	values.
> +
> +2009-11-06  Vladimir Prus  <vladimir@codesourcery.com>
> +
>          Prevent program output from mix with "^running".
>  
>  	gdb/
> Index: gdb/m68k-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/m68k-tdep.c,v
> retrieving revision 1.145
> diff -u -p -r1.145 m68k-tdep.c
> --- gdb/m68k-tdep.c	7 Sep 2009 17:52:41 -0000	1.145
> +++ gdb/m68k-tdep.c	6 Nov 2009 17:21:57 -0000
> @@ -192,7 +192,8 @@ m68k_convert_register_p (struct gdbarch 
>    if (!gdbarch_tdep (gdbarch)->fpregs_present)
>      return 0;
>    return (regnum >= M68K_FP0_REGNUM && regnum <= M68K_FP0_REGNUM + 7
> -	  && type != m68881_ext_type (gdbarch));
> +	  && type != m68881_ext_type (gdbarch)
> +	  && type != register_type (gdbarch, M68K_FP0_REGNUM));
>  }
>  
>  /* Read a value of type TYPE from register REGNUM in frame FRAME, and
> 


  parent reply	other threads:[~2009-11-06 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 13:04 Vladimir Prus
2009-11-06 13:18 ` Mark Kettenis
2009-11-06 13:23 ` Pedro Alves
2009-11-06 17:25   ` Vladimir Prus
2009-11-06 18:36     ` Daniel Jacobowitz
2009-11-06 19:27       ` Vladimir Prus
2009-11-06 23:27     ` Mark Kettenis [this message]
2009-11-07 11:02       ` Vladimir Prus
2009-11-08 12:29         ` Mark Kettenis

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=200911062325.nA6NPZHv008499@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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