public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] Update links to Arm docs Date: Thu, 17 Sep 2020 17:16:24 +0000 (GMT) [thread overview] Message-ID: <20200917171624.04A3A3A4781A@sourceware.org> (raw) https://gcc.gnu.org/g:17ad85243f3c8a98cb0647eb00c35bac639617f3 commit 17ad85243f3c8a98cb0647eb00c35bac639617f3 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Fri Aug 21 19:07:06 2020 +0100 Update links to Arm docs gcc/ * doc/extend.texi: Update links to Arm docs. * doc/invoke.texi: Likewise. (cherry picked from commit 09698e44c766c4a05ee463d2e36bc1fdac21dce4) (cherry picked from commit 0fc33daacbdf993ab0d5830b0af3468b0df7c187) Diff: --- gcc/doc/extend.texi | 6 +++--- gcc/doc/invoke.texi | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 5cd33772104..08cc1fdddfc 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -13585,12 +13585,12 @@ long long __builtin_arm_wzero () GCC implements extensions for C as described in the ARM C Language Extensions (ACLE) specification, which can be found at -@uref{http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf}. +@uref{https://developer.arm.com/documentation/ihi0053/latest/}. As a part of ACLE, GCC implements extensions for Advanced SIMD as described in the ARM C Language Extensions Specification. The complete list of Advanced SIMD intrinsics can be found at -@uref{http://infocenter.arm.com/help/topic/com.arm.doc.ihi0073a/IHI0073A_arm_neon_intrinsics_ref.pdf}. +@uref{https://developer.arm.com/documentation/ihi0073/latest/}. The built-in intrinsics for the Advanced SIMD extension are available when NEON is enabled. @@ -13621,7 +13621,7 @@ void __builtin_arm_set_fpscr (unsigned int) GCC implements the ARMv8-M Security Extensions as described in the ARMv8-M Security Extensions: Requirements on Development Tools Engineering Specification, which can be found at -@uref{http://infocenter.arm.com/help/topic/com.arm.doc.ecm0359818/ECM0359818_armv8m_security_extensions_reqs_on_dev_tools_1_0.pdf}. +@uref{https://developer.arm.com/documentation/ecm0359818/latest/}. As part of the Security Extensions GCC implements two new function attributes: @code{cmse_nonsecure_entry} and @code{cmse_nonsecure_call}. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index e48ccce1c6e..47126319e72 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -16745,7 +16745,7 @@ MOVT instruction. @opindex mcmse Generate secure code as per the "ARMv8-M Security Extensions: Requirements on Development Tools Engineering Specification", which can be found on -@url{http://infocenter.arm.com/help/topic/com.arm.doc.ecm0359818/ECM0359818_armv8m_security_extensions_reqs_on_dev_tools_1_0.pdf}. +@url{https://developer.arm.com/documentation/ecm0359818/latest/}. @end table @node AVR Options
reply other threads:[~2020-09-17 17:16 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=20200917171624.04A3A3A4781A@sourceware.org \ --to=jakub@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).