public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-8083] i386: move non-target attributes out of target section Date: Fri, 9 Apr 2021 11:47:55 +0000 (GMT) [thread overview] Message-ID: <20210409114755.2687A385E02C@sourceware.org> (raw) https://gcc.gnu.org/g:bdce43ce5a584ab329f94aef39260dd39ed530eb commit r11-8083-gbdce43ce5a584ab329f94aef39260dd39ed530eb Author: Martin Liska <mliska@suse.cz> Date: Tue Apr 6 14:18:49 2021 +0200 i386: move non-target attributes out of target section gcc/ChangeLog: * doc/extend.texi: Move non-target attributes on the top level. Diff: --- gcc/doc/extend.texi | 58 ++++++++++++++++++++++++++--------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 29ef0d67551..849c8802473 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -6924,6 +6924,35 @@ Specify which floating-point unit to use. You must specify the @code{target("fpmath=sse+387")} because the comma would separate different options. +@item prefer-vector-width=@var{OPT} +@cindex @code{prefer-vector-width} function attribute, x86 +On x86 targets, the @code{prefer-vector-width} attribute informs the +compiler to use @var{OPT}-bit vector width in instructions +instead of the default on the selected platform. + +Valid @var{OPT} values are: + +@table @samp +@item none +No extra limitations applied to GCC other than defined by the selected platform. + +@item 128 +Prefer 128-bit vector width for instructions. + +@item 256 +Prefer 256-bit vector width for instructions. + +@item 512 +Prefer 512-bit vector width for instructions. +@end table + +On the x86, the inliner does not inline a +function that has different target options than the caller, unless the +callee has a subset of the target options of the caller. For example +a function declared with @code{target("sse3")} can inline a function +with @code{target("sse2")}, since @code{-msse3} implies @code{-msse2}. +@end table + @item indirect_branch("@var{choice}") @cindex @code{indirect_branch} function attribute, x86 On x86 targets, the @code{indirect_branch} attribute causes the compiler @@ -7027,35 +7056,6 @@ On x86 targets, the @code{fentry_section} attribute sets the name of the section to record function entry instrumentation calls in when enabled with @option{-pg -mrecord-mcount} -@item prefer-vector-width=@var{OPT} -@cindex @code{prefer-vector-width} function attribute, x86 -On x86 targets, the @code{prefer-vector-width} attribute informs the -compiler to use @var{OPT}-bit vector width in instructions -instead of the default on the selected platform. - -Valid @var{OPT} values are: - -@table @samp -@item none -No extra limitations applied to GCC other than defined by the selected platform. - -@item 128 -Prefer 128-bit vector width for instructions. - -@item 256 -Prefer 256-bit vector width for instructions. - -@item 512 -Prefer 512-bit vector width for instructions. -@end table - -@end table - -On the x86, the inliner does not inline a -function that has different target options than the caller, unless the -callee has a subset of the target options of the caller. For example -a function declared with @code{target("sse3")} can inline a function -with @code{target("sse2")}, since @code{-msse3} implies @code{-msse2}. @end table @node Xstormy16 Function Attributes
reply other threads:[~2021-04-09 11:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210409114755.2687A385E02C@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).