From: "Uros Bizjak" <ubizjak@gmail.com>
To: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: [DOC PATCH]: Document new __float128 x86_64 builtin functions
Date: Fri, 08 Jun 2007 11:18:00 -0000 [thread overview]
Message-ID: <5787cf470706080316u11be1853v5c86ed2e95b567ad@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
Hello!
This doc patch adds the documentation about newly introduced
__float128 x86_64 built-in functions.
Patch was tested by 'make doc'. OK for mainline?
2007-06-08 Uros Bizjak <ubizjak@gmail.com>
* doc/extend.texi (X86 Built-in Functions): Document __builtin_fabsq,
__builtin_copysignq and __builtin_infq built-in functions.
Uros.
[-- Attachment #2: doc-copysignq.diff.txt --]
[-- Type: text/plain, Size: 1153 bytes --]
Index: extend.texi
===================================================================
--- extend.texi (revision 125566)
+++ extend.texi (working copy)
@@ -7034,6 +7034,26 @@
entire vector register, interpreting it as a 128-bit integer, these use mode
@code{TI}.
+In the 64-bit mode, x86-64 family of processors uses additional built-in
+functions for efficient use of @code{TF} (@code{__float128}) 128-bit
+floating point and @code{TC} 128-bit complex floating point values.
+
+The following floating point built-in functions are made available in the
+64-bit mode. All of them implement the function that is part of the name.
+
+@smallexample
+__float128 __builtin_fabsq (__float128)
+__float128 __builtin_copysignq (__float128, __float128)
+@end smallexample
+
+The following floating point built-in functions are made available in the
+64-bit mode.
+
+@table @code
+@item __float128 __builtin_infq (void)
+Similar to @code{__builtin_inf}, except the return type is @code{__float128}.
+@end table
+
The following built-in functions are made available by @option{-mmmx}.
All of them generate the machine instruction that is part of the name.
next reply other threads:[~2007-06-08 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 11:18 Uros Bizjak [this message]
2007-07-28 23:50 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5787cf470706080316u11be1853v5c86ed2e95b567ad@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).