From: "Michael Snyder" <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH]: fix compiler warning in java val_print.
Date: Thu, 27 Apr 2000 08:30:00 -0000 [thread overview]
Message-ID: <8e9m55$8g0$1@cronkite.cygnus.com> (raw)
In-Reply-To: <3907C293.FC355931@cygnus.com>
Andrew Cagney wrote in message < 3907C293.FC355931@cygnus.com >...
>Michael Snyder wrote:
>>
>> This (a declaration for a function argument) gets rid of
>> a gcc -Wall warning in jv-valprint.c:
>>
>> 2000-04-26 Michael Snyder <msnyder@seadog.cygnus.com>
>>
>> * jv-valprint.c (java_val_print): add arg declaration,
>> fix compiler warning.
>
>Michael,
>
>Just assume you can check these changes in.
Checked in.
>> Index: jv-valprint.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/jv-valprint.c,v
>> retrieving revision 1.1.1.6
>> diff -p -r1.1.1.6 jv-valprint.c
>> *** jv-valprint.c 2000/02/02 00:21:08 1.1.1.6
>> --- jv-valprint.c 2000/04/26 21:19:11
>> *************** java_val_print (type, valaddr, embedded_
>> *** 454,459 ****
>> --- 454,460 ----
>> deref_ref, recurse, pretty)
>> struct type *type;
>> char *valaddr;
>> + int embedded_offset;
>> CORE_ADDR address;
>> struct ui_file *stream;
>> int format;
WARNING: multiple messages have this Message-ID
From: "Michael Snyder" <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: fix compiler warning in java val_print.
Date: Wed, 05 Sep 2001 00:14:00 -0000 [thread overview]
Message-ID: <8e9m55$8g0$1@cronkite.cygnus.com> (raw)
Message-ID: <20010905001400.MBkGSqKejwLk5re8qynd0jGPzOcprh_xSJmKpklV7pE@z> (raw)
In-Reply-To: <3907C293.FC355931@cygnus.com>
Andrew Cagney wrote in message <3907C293.FC355931@cygnus.com>...
>Michael Snyder wrote:
>>
>> This (a declaration for a function argument) gets rid of
>> a gcc -Wall warning in jv-valprint.c:
>>
>> 2000-04-26 Michael Snyder <msnyder@seadog.cygnus.com>
>>
>> * jv-valprint.c (java_val_print): add arg declaration,
>> fix compiler warning.
>
>Michael,
>
>Just assume you can check these changes in.
Checked in.
>> Index: jv-valprint.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/jv-valprint.c,v
>> retrieving revision 1.1.1.6
>> diff -p -r1.1.1.6 jv-valprint.c
>> *** jv-valprint.c 2000/02/02 00:21:08 1.1.1.6
>> --- jv-valprint.c 2000/04/26 21:19:11
>> *************** java_val_print (type, valaddr, embedded_
>> *** 454,459 ****
>> --- 454,460 ----
>> deref_ref, recurse, pretty)
>> struct type *type;
>> char *valaddr;
>> + int embedded_offset;
>> CORE_ADDR address;
>> struct ui_file *stream;
>> int format;
next parent reply other threads:[~2000-04-27 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39076237.3F6A@cygnus.com>
[not found] ` <3907C293.FC355931@cygnus.com>
2000-04-27 8:30 ` Michael Snyder [this message]
2001-09-05 0:14 ` Michael Snyder
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='8e9m55$8g0$1@cronkite.cygnus.com' \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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