From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] gnu-v3-abi.c:430: warning: assignment from incompatible pointer type
Date: Thu, 16 Sep 2004 18:39:00 -0000 [thread overview]
Message-ID: <20040916183927.GA24773@nevyn.them.org> (raw)
In-Reply-To: <4149D7A5.1020900@gnu.org>
On Thu, Sep 16, 2004 at 02:12:53PM -0400, Andrew Cagney wrote:
> Hello,
>
> Using FC3's GCC 3.4, I'm seeing the warning:
>
> /home/cygnus/cagney/GDB/src/gdb/gnu-v3-abi.c: In function `init_gnuv3_ops':
> /home/cygnus/cagney/GDB/src/gdb/gnu-v3-abi.c:430: warning: assignment
> from incom
> patible pointer type
> /home/cygnus/cagney/GDB/src/gdb/gnu-v3-abi.c:431: warning: assignment
> from incom
> patible pointer type
>
> I'm not sure how it should be fixed (it's messy, see patch for
> description) - suggestions? For the moment I've disabled -Werror on
> that file.
We could remove the ctor_kinds/dtor_kinds types from the header and use
the gnu_v3 enums provided by the demangler. They're misnamed for our
purposes, but they're also a superset of what's available in other ABIs
we currently support.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-09-16 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 18:15 Andrew Cagney
2004-09-16 18:39 ` 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=20040916183927.GA24773@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--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