From: "Richard Guenther" <richard.guenther@gmail.com>
To: Gellerich <gelleric@tuxmaker.boeblingen.de.ibm.com>
Cc: gcc-patches@gcc.gnu.org, gellerich@de.ibm.com
Subject: Re: [PATCH] add insn implementing signbit to middle end and s390
Date: Tue, 03 Apr 2007 13:50:00 -0000 [thread overview]
Message-ID: <84fc9c000704030650h5577a8cfg9723b04ba1b0f3aa@mail.gmail.com> (raw)
In-Reply-To: <200704031335.l33DZOvv020696@tuxmkge1.boeblingen.de.ibm.com>
On 4/3/07, Gellerich <gelleric@tuxmaker.boeblingen.de.ibm.com> wrote:
>
> Here is the reworked version.
>
> Concerning documentation: I would provide a description for the
> "Standard Pattern Names..." section in a separate patch. However, I
> saw that a quite similar pattern named isinf is not mentioned
> there. Is this pattern intentionally omitted, or should I add a
> description for that one, too?
Probably the nitpicking please-add-documentation was missing on its addition ;)
So, if you are at it it would be nice if you can add documentation for
that one, too.
Thanks,
Richard.
next prev parent reply other threads:[~2007-04-03 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 13:35 Gellerich
2007-04-03 13:50 ` Richard Guenther [this message]
2007-04-11 7:46 ` gellerich
2007-04-11 7:46 ` gellerich
2007-04-11 7:46 ` gellerich
2007-04-11 8:54 ` gellerich
2007-04-03 14:02 ` Paolo Bonzini
2007-04-11 10:17 ` gellerich
-- strict thread matches above, loose matches on Subject: below --
2007-04-03 14:18 Uros Bizjak
2007-04-11 12:58 ` gellerich
2007-04-12 6:59 ` Uros Bizjak
2007-04-30 15:05 ` Wolfgang Gellerich
2007-03-30 9:36 Wolfgang Gellerich
2007-03-30 14:49 ` Ulrich Weigand
2007-03-30 17:24 ` Richard Henderson
2007-04-02 7:57 ` Wolfgang Gellerich
2007-04-30 17:02 ` Wolfgang Gellerich
2007-06-11 9:25 ` Richard Guenther
2007-07-06 15:02 ` Wolfgang Gellerich
2007-07-06 15:37 ` Wolfgang Gellerich
2007-07-06 16:22 ` Richard Guenther
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=84fc9c000704030650h5577a8cfg9723b04ba1b0f3aa@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gelleric@tuxmaker.boeblingen.de.ibm.com \
--cc=gellerich@de.ibm.com \
/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).