diff options
| author | Laurynas Biveinis <laurynas.biveinis@gmail.com> | 2009-04-22 04:48:34 +0000 |
|---|---|---|
| committer | Laurynas Biveinis <lauras@gcc.gnu.org> | 2009-04-22 04:48:34 +0000 |
| commit | 3cabd6d17c8ea1b9a2a7cd666339eb07e736ac6e (patch) | |
| tree | fd5b391992d702a834e6c7d9b01f77bb4d0f61fb /gcc/except.c | |
| parent | 270d1bcd872941a085c433b14499cb91fca6e66c (diff) | |
| download | gcc-3cabd6d17c8ea1b9a2a7cd666339eb07e736ac6e.zip gcc-3cabd6d17c8ea1b9a2a7cd666339eb07e736ac6e.tar.gz gcc-3cabd6d17c8ea1b9a2a7cd666339eb07e736ac6e.tar.bz2 | |
cfghooks.c (tidy_fallthru_edges): Remove find_basic_blocks references from comments.
2009-04-22 Laurynas Biveinis <laurynas.biveinis@gmail.com>
* cfghooks.c (tidy_fallthru_edges): Remove find_basic_blocks
references from comments.
* cfgbuild.c: (count_basic_blocks): Delete.
(find_basic_blocks_1): Delete.
(find_basic_blocks): Delete.
* except.c (finish_eh_generation): Make static. Move comment
from
except.h here. Remove find_basic_blocks references from
comments.
* except.h (finish_eh_generation): Delete.
* basic-block.h (find_basic_blocks): Delete.
* config/sh/sh.c (sh_output_mi_thunk): Delete a "#if 0" block.
From-SVN: r146544
Diffstat (limited to 'gcc/except.c')
| -rw-r--r-- | gcc/except.c | 22 |
1 files changed, 13 insertions, 9 deletions
diff --git a/gcc/except.c b/gcc/except.c index bc3b8c4..5a04fa6 100644 --- a/gcc/except.c +++ b/gcc/except.c @@ -2117,7 +2117,10 @@ sjlj_build_landing_pads (void) free (lp_info); } -void +/* After initial rtl generation, call back to finish generating + exception support code. */ + +static void finish_eh_generation (void) { basic_block bb; @@ -2126,14 +2129,15 @@ finish_eh_generation (void) if (cfun->eh->region_tree == NULL) return; - /* The object here is to provide find_basic_blocks with detailed - information (via reachable_handlers) on how exception control - flows within the function. In this first pass, we can include - type information garnered from ERT_THROW and ERT_ALLOWED_EXCEPTIONS - regions, and hope that it will be useful in deleting unreachable - handlers. Subsequently, we will generate landing pads which will - connect many of the handlers, and then type information will not - be effective. Still, this is a win over previous implementations. */ + /* The object here is to provide detailed information (via + reachable_handlers) on how exception control flows within the + function for the CFG construction. In this first pass, we can + include type information garnered from ERT_THROW and + ERT_ALLOWED_EXCEPTIONS regions, and hope that it will be useful + in deleting unreachable handlers. Subsequently, we will generate + landing pads which will connect many of the handlers, and then + type information will not be effective. Still, this is a win + over previous implementations. */ /* These registers are used by the landing pads. Make sure they have been generated. */ |