From: Uros Bizjak <ubizjak@gmail.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc-patches@gcc.gnu.org,
Michael Zolotukhin <michael.v.zolotukhin@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] Intrinsics for RDSEED
Date: Mon, 30 Jul 2012 13:12:00 -0000 [thread overview]
Message-ID: <CAFULd4YkKX0BZqbeVJMD+hxzyfvS4FJJ2UOv53RJb4aKFCj58A@mail.gmail.com> (raw)
On Mon, Jul 30, 2012 at 2:05 PM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
> ChangeLog entry:
> 2012-07-25 Kirill Yukhin <kirill.yukhin@intel.com>
> Michael Zolotukhin <michael.v.zolotukhin@intel.com>
>
> * common/config/i386/i386-common.c (OPTION_MASK_ISA_RDSEED_SET): New.
> (OPTION_MASK_ISA_RDSEED_UNSET): Likewise.
> (ix86_handle_option): Handle mrdseed option.
> * config.gcc (i[34567]86-*-*): Add rdseedintrin.h.
> (x86_64-*-*): Likewise.
> * config/i386/prfchwintrin.h: New header.
> * config/i386/cpuid.h (bit_RDSEED): New.
> * config/i386/driver-i386.c (host_detect_local_cpu): Detect
> RDSEED support.
> * config/i386/i386-c.c: Define __RDSEED__ if needed.
> * config/i386/i386.c (ix86_target_string): Define
> -mrdseed option.
> (PTA_RDSEED): New.
> (ix86_option_override_internal): Handle new option.
> (ix86_valid_target_attribute_inner_p): Add OPT_mrdseed.
> (ix86_builtins): Add enum entries for RDSEED* builtins.
> (ix86_init_mmx_sse_builtins): Define new builtins.
> (ix86_expand_builtin): Expand RDSEED* builtins.
> * config/i386/i386.h (TARGET_RDSEED): New.
> * config/i386/i386.md (rdseed<mode>_1): New.
> * config/i386/i386.opt (mrdseed): New.
> * config/i386/x86intrin.h: Include rdseedintrin.h.
>
> testsuite/ChangeLog unchanged.
Please put new insn pattern just after rdrnd<mode>_1 pattern in the
i386.md file.
OK with that change.
Thanks,
Uros.
next reply other threads:[~2012-07-30 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 13:12 Uros Bizjak [this message]
2012-07-30 13:56 ` Kirill Yukhin
2012-08-26 13:12 ` 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=CAFULd4YkKX0BZqbeVJMD+hxzyfvS4FJJ2UOv53RJb4aKFCj58A@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=michael.v.zolotukhin@gmail.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).