Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: vladimir@codesourcery.com (Vladimir Prus), gdb-patches@sourceware.org
Subject: Re: [2/10] Remove &builtin_type_ from tdep code         (amd64/s390/sparc64)
Date: Tue, 12 Jun 2007 16:07:00 -0000	[thread overview]
Message-ID: <200706121607.l5CG70SQ000626@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070612151452.GB16068@caradoc.them.org> from "Daniel Jacobowitz" at Jun 12, 2007 11:14:52 AM

Daniel Jacobowitz wrote:
> On Sat, Jun 09, 2007 at 01:14:58AM +0200, Ulrich Weigand wrote:
> > Hello,
> > 
> > a number of platforms (amd64, s390, sparc64) were using a global data
> > structure containing pointers to types describing the register types.
> > This is broken if those types need to be platform-specific.
> > 
> > The following patch removes those global data structures, and converts
> > the affected architectures to simply return the types dynamically from
> > the register_type callback, as all other platforms do as well.
> 
> In-flight collision warning: the m68k ColdFire patch may reintroduce an
> occurance of this, for the long double type.

Ah, good catch: 

+  /* Type of an fpreg.  NULL if there are no fpregs.  This is a
+     pointer to the pointer to type struct, because when architecture
+     init function is running, the types for the old architecture are swapped
+     out, and the types for the new architecture are not yet swapped in,
+     so all types that don't have specific sizes (like builting_type_double)
+     are NULL.  */
+  struct type **fpreg_type;

Vladimir, would you mind rewriting this?  I'd suggest to remove the
fpreg_type variable, and instead check the "flavour" in m68k_register_type.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-06-12 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 23:15 Ulrich Weigand
2007-06-12 15:09 ` Daniel Jacobowitz
2007-06-12 15:57   ` Ulrich Weigand
2007-06-12 15:14 ` Daniel Jacobowitz
2007-06-12 16:07   ` Ulrich Weigand [this message]
2007-06-13  7:08   ` Vladimir Prus
2007-06-13 13:06     ` Ulrich Weigand
2007-06-13 13:09       ` Daniel Jacobowitz
2007-06-13 13:17         ` Ulrich Weigand
2007-06-13 13:36           ` Daniel Jacobowitz
2007-06-13 13:57             ` Ulrich Weigand

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=200706121607.l5CG70SQ000626@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --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