From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [PATCH] gdb_ari.sh cleanup
Date: Thu, 16 Apr 2009 23:39:00 -0000 [thread overview]
Message-ID: <001f01c9beec$934dd280$b9e97780$@u-strasbg.fr> (raw)
I decided to go along recommendations of
removing all old macros in gdb_ari.sh.
I removed all macros that only appear in
ChangeLog entries other than current ChangeLog
and ChangeLog-2008.
I did not handle two macros, because
they are unused but are still present in docs:
REGISTER_U_ADDR
PROCESS_LINENUMBER_HOOK
Miscellaneous questions:
1a) Should the PARAMS rule be moved to code section?
1b) Same question for __FUNCTION__ rule.
1c) Idem for ARGSUSED
1d) Idem for
2) LITTLE_ENDIAN and BIG_ENDIAN still exists in configure,
should I still remove the rule?
3) HAVE_VFORK is still present in config.in
should I keep the rule or should we remove it from config.in first?
I send here only the list of
BEGIN lines of the rules that I removed:
Pierre Muller
Pascal language support maintainer for GDB
< BEGIN { doc["FETCH_INFERIOR_REGISTERS"] = "\
< BEGIN { doc["CANNOT_FETCH_REGISTER"] = "\
< BEGIN { doc["CHILD_(|POST_)WAIT"] = "\
< BEGIN { doc["CHILD_POST_ATTACH"] = "\
< BEGIN { doc["CHILD_THREAD_ALIVE"] = "\
< BEGIN { doc["CHILD_PREPARE_TO_STORE"] = "\
< BEGIN { doc["CHILD_POST_STARTUP_INFERIOR"] = "\
< BEGIN { doc["CHILD_ACKNOWLEDGE_CREATED_INFERIOR"] = "\
< BEGIN { doc["CHILD_(INSERT|REMOVE)_FORK_CATCHPOINT"] = "\
< BEGIN { doc["CHILD_(INSERT|REMOVE)_VFORK_CATCHPOINT"] = "\
< BEGIN { doc["CHILD_(INSERT|REMOVE)_EXEC_CATCHPOINT"] = "\
< BEGIN { doc["CHILD_FOLLOW_FORK"] = "\
< BEGIN { doc["CHILD_REPORTED_EXEC_EVENTS_PER_EXEC_CALL"] = "\
< BEGIN { doc["CHILD_HAS_EXITED"] = "\
< BEGIN {
doc["CHILD_(ENABLE_EXCEPTION_CALLBACK|GET_CURRENT_EXCEPTION_EVENT)"] = "\
< BEGIN { doc["CHILD_PID_TO_(EXEC_FILE|STR)"] = "\
< BEGIN { doc["HAVE_OPTIONAL_PROC_FS"] = "\
< BEGIN { doc["VARIABLES_INSIDE_BLOCK"] = "\
< BEGIN { doc["TEXT_SEGMENT_BASE"] = "\
< BEGIN { doc["STATIC_TRANSFORM_NAME"] = "\
< BEGIN { doc["SOFUN_ADDRESS_MAYBE_MISSING"] = "\
< BEGIN { doc["SKIP_PERMANENT_BREAKPOINT"] = "\
< BEGIN { doc["SIGCONTEXT_REGISTER_ADDRESS"] = "\
< BEGIN { doc["SETUP_ARBITRARY_FRAME"] = "\
< BEGIN { doc["NUM_REALREGS"] = "\
< BEGIN { doc["LOWEST_PC"] = "\
< BEGIN { doc["IS_STATIC_TRANSFORM_NAME"] = "\
< BEGIN { doc["GDB_TARGET_IS_HPPA_20W"] = "\
< BEGIN { doc["CLEAR_SOLIB"] = "\
< BEGIN { doc["CHILD_SPECIAL_WAITSTATUS"] = "\
< BEGIN { doc["CHILD_GET_CURRENT_EXCEPTION_EVENT"] = "\
< BEGIN { doc["CHILD_ENABLE_EXCEPTION_CALLBACK"] = "\
< BEGIN { doc["HOST_BYTE_ORDER"] = "\
< BEGIN { doc["USG"] = "\
< BEGIN { doc["EXTRACT_RETURN_VALUE"] = "\
< BEGIN { doc["STORE_RETURN_VALUE"] = "\
next reply other threads:[~2009-04-16 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 23:39 Pierre Muller [this message]
2009-04-17 0:19 ` Joel Brobecker
2009-04-17 6:39 ` Pierre Muller
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='001f01c9beec$934dd280$b9e97780$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.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