public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-5891] arm: libgcc: tweak warning from __sync_synchronize Date: Mon, 27 Nov 2023 18:01:58 +0000 (GMT) [thread overview] Message-ID: <20231127180158.A77283858C2D@sourceware.org> (raw) https://gcc.gnu.org/g:eecdd96c8d1de244e21212a830e51062b3e444c5 commit r14-5891-geecdd96c8d1de244e21212a830e51062b3e444c5 Author: Richard Earnshaw <rearnsha@arm.com> Date: Mon Nov 27 17:59:39 2023 +0000 arm: libgcc: tweak warning from __sync_synchronize My previous patch to add an implementation of __sync_syncrhonize with a warning trips a testsuite failure in fortran (and possibly other languages as well) as the framework expects no blank lines in the output, but this warning was generating one. So remove the newline from the end of the message and rely on the one added by the linker instead. Since we're there, remove the trailing period from the message as well, since the convention seems to be not to have one. libgcc/ * config/arm/lib1funcs.S (__sync_synchronize): Adjust warning message. Diff: --- libgcc/config/arm/lib1funcs.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgcc/config/arm/lib1funcs.S b/libgcc/config/arm/lib1funcs.S index 78887861616..40e9a7a87fb 100644 --- a/libgcc/config/arm/lib1funcs.S +++ b/libgcc/config/arm/lib1funcs.S @@ -2214,7 +2214,7 @@ LSYM(Lchange_\register): .ascii "no effect. Relink with\n" .ascii " -specs=sync-{none,dmb,cp15dmb}.specs\n" .ascii "to specify exactly which barrier format to use and avoid " - .ascii "this warning.\n\0" + .ascii "this warning\0" #endif #endif #endif
reply other threads:[~2023-11-27 18:01 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=20231127180158.A77283858C2D@sourceware.org \ --to=rearnsha@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).