From patchwork Sun Jun 3 12:29:31 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Oleg Endo X-Patchwork-Id: 162502 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id 9831EB6FF4 for ; Sun, 3 Jun 2012 22:30:11 +1000 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1339331412; h=Comment: DomainKey-Signature:Received:Received:Received:Received:Received: Message-ID:Subject:From:To:Date:Content-Type:Mime-Version: Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:Sender:Delivered-To; bh=FZPx/9TOPoEgyQrsGpjC UQZTMpA=; b=TZJl6lPaMO5sP9ZxsLV6KAaSz9sPERxnMO/SBYkUqMvmd1yHtnVq 5vtQY9uG8jgo0kqy1/aYbn95HaesuXal3ETX1s/5kXB6yG7xktltamlz/ni68sZG Xw3mvFYFr8JtoLIs41GslUJUsh/Re/ByPc15V68/F7mV1Gef3C1dblI= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:Received:Message-ID:Subject:From:To:Date:Content-Type:Mime-Version:X-IsSubscribed:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=KSc6LPoj8o1sfJI5deWvJ5bQ9wOerfEteCimo1T/60KY2VCJL6ZgDOwQeiQVdh 9jD9jCcks1pl365NHzf11ODNWxd/yRXe7am1U0ZRQep8T45DnP8gfC4cHHKBMuU1 eSgvEkmIPbryxx3Sm6f8N6/TI6f86njdyjevAFiNBlVUA=; Received: (qmail 32204 invoked by alias); 3 Jun 2012 12:30:06 -0000 Received: (qmail 32142 invoked by uid 22791); 3 Jun 2012 12:30:05 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_NONE, RCVD_IN_HOSTKARMA_NO, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from mailout06.t-online.de (HELO mailout06.t-online.de) (194.25.134.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 03 Jun 2012 12:29:38 +0000 Received: from fwd16.aul.t-online.de (fwd16.aul.t-online.de ) by mailout06.t-online.de with smtp id 1Sb9w8-0004wJ-I3; Sun, 03 Jun 2012 14:29:36 +0200 Received: from [192.168.0.104] (GWNKj2ZbQhn3dGiPrFTeje4Xa65EeVd8SpXHT9LnWPtv+r39LQX4kwkENA5vgAdQGh@[87.157.38.241]) by fwd16.t-online.de with esmtp id 1Sb9w3-0Rd8gy0; Sun, 3 Jun 2012 14:29:31 +0200 Message-ID: <1338726571.2493.4.camel@yam-132-YW-E178-FTW> Subject: Document sincos standard pattern name From: Oleg Endo To: gcc-patches Date: Sun, 03 Jun 2012 14:29:31 +0200 Mime-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org Hi, The attached patch adds some documentation for the sincos standard pattern name. Tested with 'make info dvi pdf'. Is the text correct and OK to apply? Maybe it would also make sense to apply it to the 4.7 branch? Cheers, Oleg ChangeLog: * gcc/doc/md.texi (Standard Pattern Names For Generation): Document sincos pattern. Index: gcc/doc/md.texi =================================================================== --- gcc/doc/md.texi (revision 188148) +++ gcc/doc/md.texi (working copy) @@ -4795,6 +4795,22 @@ built-in function uses the mode which corresponds to the C data type @code{float}. +@cindex @code{sincos@var{m}3} instruction pattern +@item @samp{sincos@var{m}3} +Store the sine of operand 2 into operand 0 and the cosine of +operand 2 into operand 1. + +The @code{sin} and @code{cos} built-in functions of C always use the +mode which corresponds to the C data type @code{double} and the +@code{sinf} and @code{cosf} built-in function use the mode which +corresponds to the C data type @code{float}. +Targets that can calculate the sine and cosine simultaneously can +implement this pattern as opposed to implementing individual +@code{sin@var{m}2} and @code{cos@var{m}2} patterns. The @code{sin} +and @code{cos} built-in functions will then be expanded to the +@code{sincos@var{m}3} pattern, with one of the output values +left unused. + @cindex @code{exp@var{m}2} instruction pattern @item @samp{exp@var{m}2} Store the exponential of operand 1 into operand 0.