Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Makefile.in: no ,-Werror for thread-db.c
Date: Fri, 26 Apr 2002 14:12:00 -0000	[thread overview]
Message-ID: <20020426171241.A4283@nevyn.them.org> (raw)
In-Reply-To: <15561.47290.123521.894587@localhost.redhat.com>

On Fri, Apr 26, 2002 at 04:29:46PM -0400, Elena Zannoni wrote:
> 
> I keep getting warnings for thread-db.c about mismatched types:
> 
> /home/ezannoni/uberbaum/src/gdb/thread-db.c: In function `thread_db_fetch_registers':
> /home/ezannoni/uberbaum/src/gdb/thread-db.c:805: warning: passing arg 1 of `supply_fpregset' from incompatible pointer type
> /home/ezannoni/uberbaum/src/gdb/thread-db.c: In function `thread_db_store_registers':
> /home/ezannoni/uberbaum/src/gdb/thread-db.c:838: warning: passing arg 1 of `fill_fpregset' from incompatible pointer type
> /home/ezannoni/uberbaum/src/gdb/thread-db.c:844: warning: passing arg 2 of pointer to function from incompatible pointer type
> 
> Is this OK? ...unless somebody more familiar than me with regsets wants
> to go and fix it. :-)

This implies that your platform (PowerPC you said?) has a broken
prfpregset_t in the presence of AltiVec.  We should both get glibc
fixed and/or autoconf away the problem...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      parent reply	other threads:[~2002-04-26 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 13:30 Elena Zannoni
2002-04-26 13:53 ` Andrew Cagney
2002-04-26 14:00   ` Elena Zannoni
2002-04-26 14:14     ` Michael Snyder
2002-04-26 14:12 ` Daniel Jacobowitz [this message]

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=20020426171241.A4283@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ezannoni@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