From: Gaius Mulley <gaius@glam.ac.uk>
To: gdb-patches@sources.redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
Jim Blandy <jimb@codesourcery.com>
Subject: [commit]: Re: Enhanced language support for Modula-2
Date: Sat, 13 May 2006 16:24:00 -0000 [thread overview]
Message-ID: <87zmhlgc0y.fsf_-_@glam.ac.uk> (raw)
In-Reply-To: <vt264kbjebb.fsf@theseus.home.>
Hi,
a small note to say that I've applied the Modula-2 enhancement patches
to the gdb cvs. Many thanks for all the guidance,
regards,
Gaius
2006-05-09 Gaius Mulley <gaius@glam.ac.uk>
* gdb/m2-lang.h: added function extern prototypes for
m2_is_long_set and get_long_set_bounds.
* gm2/m2-typeprint.c: This file has been completely
replaced to reflect the Modula-2 syntax rather than call the
c_print_type function.
(m2_print_type): walk the Modula-2 type tree.
(m2_type_name): added.
(m2_range): added.
(m2_typedef): added.
(m2_array): added.
(m2_pointer): added.
(m2_ref): added.
(m2_unknown): added.
(m2_union): added.
(m2_procedure): added.
(m2_print_bounds): added.
(m2_short_set): added.
(m2_is_long_set): added.
(m2_get_discrete_bounds): added.
(m2_is_long_set_of_type): added.
(m2_long_set): added.
(m2_record_fields): added.
(m2_enum): added.
* gdb/dwarf2read.c: added ability to detect the language
Modula-2 and handle SET and CHAR types.
(read_set_type): added.
(process_die): call read_set_type.
(read_base_type): modifed signed/unsigned char handling for
Modula-2.
(set_cu_language): added Modula-2 case clause.
* gdb/m2-valprint.c: complete replacement so that Modula-2
values are printed rather than call the C language routines.
(print_function_pointer_address): added.
(get_long_set_bounds): added.
(m2_print_long_set): added.
(print_unpacked_pointer): added.
(print_variable_at_address): added.
(m2_val_print): replaced.
* gdb/doc/gdb.texinfo: added a section on Modula-2 Types.
next prev parent reply other threads:[~2006-05-13 16:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 13:23 Gaius Mulley
2006-04-20 14:35 ` Eli Zaretskii
2006-04-20 18:47 ` Mark Kettenis
2006-04-20 18:54 ` Eli Zaretskii
2006-05-04 7:17 ` Gaius Mulley
2006-05-04 15:37 ` Daniel Jacobowitz
2006-05-04 18:01 ` Jim Blandy
2006-05-08 14:09 ` Gaius Mulley
2006-05-08 17:47 ` Jim Blandy
2006-05-09 22:57 ` Gaius Mulley
2006-05-10 21:45 ` Jim Blandy
2006-05-11 12:37 ` Gaius Mulley
2006-05-12 18:18 ` Joel Brobecker
2006-05-12 18:27 ` Jim Blandy
2006-05-13 13:31 ` Gaius Mulley
2006-05-13 16:24 ` Gaius Mulley [this message]
2006-05-13 16:43 ` [commit]: " Daniel Jacobowitz
2006-05-13 18:56 ` Gaius Mulley
2006-05-13 19:08 ` Daniel Jacobowitz
2006-05-13 19:44 ` Gaius Mulley
2006-05-13 11:02 ` Gaius Mulley
2006-05-08 21:03 ` Eli Zaretskii
2006-05-04 16:12 ` Eli Zaretskii
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=87zmhlgc0y.fsf_-_@glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.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