md.texi: Note problems using function calls to determine insn lengths and point reade...

        * doc/md.texi: Note problems using function calls to determine
        insn lengths and point readers to a potential workaround.

From-SVN: r218439

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 9538737c7d78adf5498d16078084250ebbba7784..0dcf6498e320f28df3242d0f38c7efd206971921 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2014-12-05  Jeff Law  <law@redhat.com>
+
+       * doc/md.texi: Note problems using function calls to determine
+       insn lengths and point readers to a potential workaround.
+
 2014-12-05  Andreas Schwab  <schwab@linux-m68k.org>
 
        * combine.c (is_parallel_of_n_reg_sets)

diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index b8e5ac522b700e1e2af407bb8b696ea4f7696977..1c70a77399ab22cc727fd406cabde4b4cce5e49e 100644 (file)
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -8345,6 +8345,12 @@ the number of vectors multiplied by the size of each vector.
 
 Lengths are measured in addressable storage units (bytes).
 
+Note that it is possible to call functions via the @code{symbol_ref}
+mechanism to compute the length of an insn.  However, if you use this
+mechanism you must provide dummy clauses to express the maximum length
+without using the function call.  You can an example of this in the
+@code{pa} machine description for the @code{call_symref} pattern.
+
 The following macros can be used to refine the length computation:
 
 @table @code