Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	mark.kettenis@xs4all.nl,         gdb-patches@sourceware.org
Subject: Re: [patch] Fix warnings using gcc-4.5 HEAD
Date: Thu, 30 Jul 2009 00:28:00 -0000	[thread overview]
Message-ID: <m38wi7t9z1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090711175937.GB18892@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sat\, 11 Jul 2009 19\:59\:37 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> 2009-07-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
Jan> 	Fix gcc-4.5 HEAD warnings for enum ada_operator.
Jan> 	* Makefile.in (HFILES_NO_SRCDIR): Add ada-operator.inc.
Jan> 	* ada-lang.h (enum ada_operator): Move it to ...
Jan> 	* ada-operator.inc: ... a new file.
Jan> 	* expression.h (enum exp_opcode): Include ada-operator.inc.
Jan> 	New element OP_UNUSED_LAST.

I'd like Joel to comment on the Ada changes.

They seem reasonable enough to me.  I was unaware of enum ada_operator,
yikes.

At the very least, the comment above OP_EXTENDED0 needs to be updated.
It mentions the extension enum approach, which now can't be used.

Jan> 	Fix gcc-4.5 HEAD warnings for GDB_FORM_cached_string.
Jan> 	* dwarf2read.c (GDB_FORM_cached_string)
Jan> 	(dwarf_form_name <GDB_FORM_cached_string>): Remove.
Jan> 	(struct attribute <dwarf_form>): Reduce the bit width.
Jan> 	(struct attribute <string_is_canonical>, DW_STRING_IS_CANONICAL): New.
Jan> 	(read_attribute_value <DW_FORM_string>)
Jan> 	(read_attribute_value <DW_FORM_strp>): Initialize
Jan> 	DW_STRING_IS_CANONICAL.
Jan> 	(dwarf2_name, dump_die_shallow <DW_FORM_string>)
Jan> 	(dump_die_shallow <DW_FORM_strp>): Update the code using former
Jan> 	GDB_FORM_cached_string.

This part is ok.

Jan>      /* NOTE: Eventually, we expect to convert to an object-oriented 
Jan>         formulation for expression operators that does away with the
Jan>         need for these extension operators, and indeed for this
Jan>         entire enumeration type.  Therefore, consider the OP_EXTENDED
Jan>         definitions to be a temporary measure. */

This comment is nearly 6 years old :(

Tom


  reply	other threads:[~2009-07-29 22:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  8:39 Jan Kratochvil
2009-07-11  8:46 ` Mark Kettenis
2009-07-11  9:25   ` Jan Kratochvil
2009-07-11 12:09     ` Eli Zaretskii
2009-07-11 19:02       ` Jan Kratochvil
2009-07-30  0:28         ` Tom Tromey [this message]
2009-09-08 18:52           ` Jan Kratochvil
2009-09-10  1:48             ` Joel Brobecker
2009-09-10  7:29               ` Jan Kratochvil
2009-09-15 16:11                 ` Jan Kratochvil
2009-07-11  9:32   ` Eli Zaretskii
2009-07-11 20:58 ` Daniel Jacobowitz

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=m38wi7t9z1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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