From: Andrew Cagney <ac131313@redhat.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Simplify gdbarch.sh a tiny bit
Date: Thu, 10 Jul 2003 23:22:00 -0000 [thread overview]
Message-ID: <3F0DF532.90801@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0307101610020.24809@knuth.amplepower.com>
> On Thu, 10 Jul 2003, Andrew Cagney wrote:
>
>
>> Hello,
>>
>> The attached simplfies gdbarch.sh a tiny bit - it uses gdb_assert
>> instead of internal_error in a few places (from memory gdbarch.sh was
>> written before gdb_assert was added).
>
>
> I'm getting a build failure now:
Oh, flip. The bit to revert should be obvious. I'm off line for a few
hours.
Andrew
> gcc -c -g -O2 -I. -I../../gdb -I../../gdb/config
> -DLOCALEDIR="\"/home/roth/local/avr/share/locale\"" -DHAVE_CONFIG_H
> -I../../gdb/../include/opcode -I../../gdb/../readline/.. -I../bfd
> -I../../gdb/../bfd -I../../gdb/../include -I../intl
> -I../../gdb/../intl -DMI_OUT=1 -Wimplicit -Wreturn-type -Wcomment
> -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized
> -Werror ../../gdb/gdbarch.c
> cc1: warnings being treated as errors
> ../../gdb/gdbarch.c: In function
> `gdbarch_deprecated_max_register_raw_size_p':
> ../../gdb/gdbarch.c:3425: warning: comparison between pointer and integer
> ../../gdb/gdbarch.c: In function
> `gdbarch_deprecated_max_register_virtual_size_p':
> ../../gdb/gdbarch.c:3448: warning: comparison between pointer and integer
> ../../gdb/gdbarch.c: In function
> `gdbarch_deprecated_call_dummy_stack_adjust_p':
> ../../gdb/gdbarch.c:3805: warning: comparison between pointer and integer
> make: *** [gdbarch.o] Error 1
>
> Is this related to your change?
next prev parent reply other threads:[~2003-07-10 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 22:00 Andrew Cagney
2003-07-10 23:07 ` Theodore A. Roth
2003-07-10 23:22 ` Andrew Cagney [this message]
2003-07-11 1:36 ` Andrew Cagney
2003-07-11 15:23 ` Theodore A. Roth
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=3F0DF532.90801@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=troth@openavr.org \
/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