Oboguev
Cc: gcc@gcc.gnu.org
Sent: Tue, January 3, 2012 12:08:22 PM
Subject: Re: GCC/GLIBC and non-temporal instructions
Sergey Oboguev writes:
> Well, all these
>
> storent
> emit_storent_insn
> may_use_storent_in_loop
> storent_optab
Sergey Oboguev writes:
> Well, all these
>
> storent
> emit_storent_insn
> may_use_storent_in_loop
> storent_optab
> nontemporal
> assign_set_nontemporal_move
> mark_nontemporal_store
> mark_nontemporal_stores
> nontemporal_store_p
> schedule_prefetches
>
Oboguev
Cc: gcc@gcc.gnu.org
Sent: Tue, January 3, 2012 11:24:15 AM
Subject: Re: GCC/GLIBC and non-temporal instructions
Sergey Oboguev writes:
> The question is whether there is any GCC/runtime policy on non-temporal
> SSE/3DNow instructions?
As far as I know gcc will never generate a
Sergey Oboguev writes:
> The question is whether there is any GCC/runtime policy on non-temporal
> SSE/3DNow instructions?
As far as I know gcc will never generate any non-temporal instructions,
except if the programmer uses the special intrinsic functions which
generate them. If the programme
