From: Piervit <piervit@pvittet.com>
To: gcc-patches@gcc.gnu.org
Subject: external declaration of dominance debug functions
Date: Mon, 23 May 2011 09:49:00 -0000 [thread overview]
Message-ID: <20110523103355.71528d09@zenwalk.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
Hello,
Here is a two lines patch, allowing to use debug_dominance_info and
debug_dominance_tree functions outside of gcc/dominance.c. For the
moment, those functions are not declared in any gcc/*.h files (as far as
I know after trying a grep). I have added them as external functions
into gcc/basic-block.h. I feel this is useful to be able to call those
functions from others files, for exemple from plugins.
ChangeLog:
2011-05-23 Pierre Vittet <piervit@pvittet.com>
* basic-block.h (debug_dominance_info, debug_dominance_tree):
Add declaration.
[-- Attachment #2: add_dom_debug_to_header-174056.diff --]
[-- Type: text/x-patch, Size: 584 bytes --]
Index: gcc/basic-block.h
===================================================================
--- gcc/basic-block.h (revision 174056)
+++ gcc/basic-block.h (working copy)
@@ -882,6 +882,9 @@ extern basic_block get_bb_copy (basic_block);
void set_loop_copy (struct loop *, struct loop *);
struct loop *get_loop_copy (struct loop *);
+extern void debug_dominance_info (enum cdi_direction dir);
+extern void debug_dominance_tree (enum cdi_direction dir, basic_block root);
+
#include "cfghooks.h"
/* Return true when one of the predecessor edges of BB is marked with EDGE_EH. */
next reply other threads:[~2011-05-23 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:49 Piervit [this message]
2011-05-23 9:56 ` Basile Starynkevitch
2011-05-23 10:22 ` Richard Guenther
2011-05-23 10:53 ` Piervit
2011-05-23 20:55 ` Basile Starynkevitch
2011-05-23 22:52 ` Richard Guenther
2011-05-23 23:06 ` Nathan Froyd
2011-05-23 23:06 ` Richard Guenther
2011-05-24 10:42 ` Basile Starynkevitch
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=20110523103355.71528d09@zenwalk.local \
--to=piervit@pvittet.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).