[committed] arm: libgcc: tweak warning from __sync_synchronize

Message ID 20231127180209.548531-1-rearnsha@arm.com
State Committed
Commit eecdd96c8d1de244e21212a830e51062b3e444c5
Series [committed] arm: libgcc: tweak warning from __sync_synchronize |


Context Check Description
linaro-tcwg-bot/tcwg_gcc_build--master-arm warning Patch is already merged
linaro-tcwg-bot/tcwg_gcc_build--master-aarch64 warning Patch is already merged

Commit Message

Richard Earnshaw Nov. 27, 2023, 6:02 p.m. UTC
  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

Since we're there, remove the trailing period from the message as
well, since the convention seems to be not to have one.


	* config/arm/lib1funcs.S (__sync_synchronize): Adjust warning message.
 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"