GCC Middle and Back End API Reference
tree-cfgcleanup.h File Reference
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Functions

bool cleanup_tree_cfg (void)
bool fixup_noreturn_call (gimple stmt)

Variables

bitmap cfgcleanup_altered_bbs

Function Documentation

bool cleanup_tree_cfg ( void  )

Cleanup cfg and repair loop structures.

bool fixup_noreturn_call ( gimple  stmt)

Variable Documentation

bitmap cfgcleanup_altered_bbs

Header file for CFG cleanup for trees. Copyright (C) 2013 Free Software Foundation, Inc.

This file is part of GCC.

GCC is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version.

GCC is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with GCC; see the file COPYING3. If not see http://www.gnu.org/licenses/. In tree-cfgcleanup.c

CFG cleanup for trees. Copyright (C) 2001-2013 Free Software Foundation, Inc.

This file is part of GCC.

GCC is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version.

GCC is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with GCC; see the file COPYING3. If not see http://www.gnu.org/licenses/. The set of blocks in that at least one of the following changes happened: – the statement at the end of the block was changed – the block was newly created – the set of the predecessors of the block changed – the set of the successors of the block changed ??? Maybe we could track these changes separately, since they determine what cleanups it makes sense to try on the block.