From dc6729518aabcff9050c5bd04e89bccc40c24fb5 Mon Sep 17 00:00:00 2001 From: Steve Ellcey Date: Tue, 3 Mar 2009 18:33:40 +0000 Subject: re PR middle-end/10109 (documentation of target macro LIBCALL_VALUE) PR middle-end/10109 * tm.texi (LIBCALL_VALUE): Update description. From-SVN: r144586 --- gcc/ChangeLog | 5 +++++ gcc/doc/tm.texi | 10 +--------- 2 files changed, 6 insertions(+), 9 deletions(-) (limited to 'gcc') diff --git a/gcc/ChangeLog b/gcc/ChangeLog index a4a1874..f145fbe 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,5 +1,10 @@ 2009-03-03 Steve Ellcey + PR middle-end/10109 + * tm.texi (LIBCALL_VALUE): Update description. + +2009-03-03 Steve Ellcey + PR middle-end/34443 * doc/extend.texi (section): Update description. diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index a311a9f..b4fcc2d 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -4304,20 +4304,12 @@ a new target instead. @defmac LIBCALL_VALUE (@var{mode}) A C expression to create an RTX representing the place where a library -function returns a value of mode @var{mode}. If the precise function -being called is known, @var{func} is a tree node -(@code{FUNCTION_DECL}) for it; otherwise, @var{func} is a null -pointer. This makes it possible to use a different value-returning -convention for specific functions when all their calls are -known. +function returns a value of mode @var{mode}. Note that ``library function'' in this context means a compiler support routine, used to perform arithmetic, whose name is known specially by the compiler and was not mentioned in the C code being compiled. - -The definition of @code{LIBRARY_VALUE} need not be concerned aggregate -data types, because none of the library functions returns such types. @end defmac @defmac FUNCTION_VALUE_REGNO_P (@var{regno}) -- cgit v1.1