This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[doc] cfg.texi - remove two references to Java
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
- Cc: Jan Hubicka <hubicka at ucw dot cz>
- Date: Mon, 2 Jan 2017 10:23:10 -0400 (AST)
- Subject: [doc] cfg.texi - remove two references to Java
- Authentication-results: sourceware.org; auth=none
Applied.
Gerald
2017-01-02 Gerald Pfeifer <gerald@pfeifer.com>
* doc/cfg.texi (Edges): Remove reference to Java.
(Maintaining the CFG): Ditto.
Index: doc/cfg.texi
===================================================================
--- doc/cfg.texi (revision 244001)
+++ doc/cfg.texi (working copy)
@@ -285,7 +285,7 @@
Exception handling edges represent possible control transfers from a
trapping instruction to an exception handler. The definition of
``trapping'' varies. In C++, only function calls can throw, but for
-Java and Ada, exceptions like division by zero or segmentation fault are
+Ada exceptions like division by zero or segmentation fault are
defined and thus each instruction possibly throwing this kind of
exception needs to be handled as control flow instruction. Exception
edges have the @code{EDGE_ABNORMAL} and @code{EDGE_EH} flags set.
@@ -594,8 +594,7 @@
Usually a code manipulating pass simplifies the instruction stream and
the flow of control, possibly eliminating some edges. This may for
example happen when a conditional jump is replaced with an
-unconditional jump, but also when simplifying possibly trapping
-instruction to non-trapping while compiling Java. Updating of edges
+unconditional jump. Updating of edges
is not transparent and each optimization pass is required to do so
manually. However only few cases occur in practice. The pass may
call @code{purge_dead_edges} on a given basic block to remove