public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [3.4-BIB] Add trunc/round/floor/ceil/rint builtins
Date: Wed, 06 Nov 2002 10:29:00 -0000	[thread overview]
Message-ID: <20021106182857.GC22066@redhat.com> (raw)
In-Reply-To: <20021106102749.GF22059@kam.mff.cuni.cz>

On Wed, Nov 06, 2002 at 11:27:49AM +0100, Jan Hubicka wrote:
> 	* builtins.c (expand_builtin_mathfn): Handle floor/ceil/trunc/round/rint
> 	(expand_builtin): Likewise.
> 	* builtins.def: Add
> 	__builtin_floor, __builtin_floorf, __builtin_floorl
> 	__builtin_ceil, __builtin_ceilf, __builtin_ceill
> 	__builtin_round, __builtin_roundf, __builtin_roundl
> 	__builtin_trunc, __builtin_truncf, __builtin_truncl
> 	__builtin_rint, __builtin_rintf, __builtin_rintl.
> 	* genopinit.c (optabs): Initialize the new optabs.
> 	* optab.c (init_optabs): Likewise.
> 	* optabs.h (optab_index): Add OTI_floor, OTI_ceil, OTI_trunc,
> 	OTI_round, OTI_rint.
> 	(floor_optab, ceil_optab, trunc_optab, round_optab, rint_optab): New.
> 	* md.texi: Document new named patterns.

Ok, with the extend.texi hunk posted later.


r~

  parent reply	other threads:[~2002-11-06 18:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  2:27 Jan Hubicka
2002-11-06  6:03 ` Joseph S. Myers
2002-11-06  6:11   ` Jan Hubicka
2002-11-06 11:14     ` Joseph S. Myers
2002-11-06 11:29       ` Dale Johannesen
2002-11-06 13:12       ` Jan Hubicka
2002-11-06 13:18         ` Gabriel Dos Reis
2002-11-06 13:20           ` Jan Hubicka
2002-11-06 13:31             ` Gabriel Dos Reis
2002-11-06 13:35               ` Jan Hubicka
2002-11-06 13:54                 ` [3.4-BIB] Add trunc/round/floor/ceil/rint builtins II Jan Hubicka
2002-11-06 14:29                   ` Richard Henderson
2002-11-06 14:41                     ` Jan Hubicka
2002-11-06 14:52                     ` Jan Hubicka
2002-11-06 15:06                       ` Richard Henderson
2002-11-06 15:32                         ` Dale Johannesen
2002-11-06 15:48                           ` Richard Henderson
2002-11-06 15:57                             ` Dale Johannesen
2002-11-07  0:48                               ` Neil Booth
2002-11-06 16:01                             ` Joseph S. Myers
2002-11-06 16:04                               ` Richard Henderson
2002-11-07  1:10                                 ` Jan Hubicka
2002-11-07  1:08                             ` Jan Hubicka
2002-11-07  1:08                         ` Jan Hubicka
2002-11-06 16:05                       ` Joseph S. Myers
2002-11-07  1:10                         ` Jan Hubicka
2002-11-07  1:18                           ` Jan Hubicka
2002-11-07  3:05                             ` [3.4-BIB] Add trunc/round/floor/ceil/rint builtins III Jan Hubicka
2002-11-07 16:56                               ` Richard Henderson
2002-11-07  4:54                       ` [3.4-BIB] Add trunc/round/floor/ceil/rint builtins II Hans-Peter Nilsson
2002-11-06 14:04                 ` [3.4-BIB] Add trunc/round/floor/ceil/rint builtins Gabriel Dos Reis
2002-11-06 14:06                   ` Jan Hubicka
2002-11-06 14:09                     ` Gabriel Dos Reis
2002-11-06 14:04         ` Dale Johannesen
2002-11-06 10:29 ` Richard Henderson [this message]
2002-11-06 13:13   ` Jan Hubicka

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=20021106182857.GC22066@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).