public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Junxian Zhu" <zhujunxian@oss.cipunited.com>
To: <libc-alpha@sourceware.org>
Cc: <rongrong@oss.cipunited.com>,
	 "Junxian Zhu" <zhujunxian@oss.cipunited.com>
Subject: [PATCH 1/2] limb-alias-double.h: Fix missing semicolon
Date: Mon, 25 Dec 2023 18:35:48 +0800	[thread overview]
Message-ID: <20231225103548.1615-3-zhujunxian@oss.cipunited.com> (raw)
In-Reply-To: <20231225103548.1615-2-zhujunxian@oss.cipunited.com>

From: Junxian Zhu <zhujunxian@oss.cipunited.com>

MIPS o32 defined NO_LONG_DOUBLE. Missing semicolon at the end of weak_alias and strong_alias will cause syntax error during assembly building.

Signed-off-by: Rong Zhang <rongrong@oss.cipunited.com>
Signed-off-by: Junxian Zhu <zhujunxian@oss.cipunited.com>
---
 sysdeps/generic/libm-alias-double.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sysdeps/generic/libm-alias-double.h b/sysdeps/generic/libm-alias-double.h
index 65ba382da9..e68f1e5ad6 100644
--- a/sysdeps/generic/libm-alias-double.h
+++ b/sysdeps/generic/libm-alias-double.h
@@ -56,8 +56,8 @@
    obsolescent functions not provided for _FloatN types.  */
 #ifdef NO_LONG_DOUBLE
 # define libm_alias_double_r(from, to, r)	\
-  weak_alias (from ## r, to ## r)		\
-  strong_alias (from ## r, from ## l ## r)	\
+  weak_alias (from ## r, to ## r);		\
+  strong_alias (from ## r, from ## l ## r);	\
   weak_alias (from ## r, to ## l ## r);		\
   libm_alias_double_other_r (from, to, r)
 #else
-- 
2.43.0.windows.1

  reply	other threads:[~2023-12-25 10:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25 10:35 [PATCH 0/2] Add hard-float rounding instructions support for MIPS architecture Junxian Zhu
2023-12-25 10:35 ` Junxian Zhu [this message]
2023-12-25 10:35 ` [PATCH 2/2] MIPS: Hard-float rounding instructions support Junxian Zhu
2023-12-25 10:51   ` Xi Ruoyao
2023-12-26  2:37     ` Junxian Zhu
2023-12-26  8:29       ` Xi Ruoyao
2023-12-26 20:12         ` Adhemerval Zanella Netto
2023-12-26 21:50           ` Xi Ruoyao
2023-12-26 22:50             ` Xi Ruoyao
2023-12-27 13:25               ` Adhemerval Zanella Netto
2024-01-02 10:08               ` Junxian Zhu
2024-01-02  9:43         ` Junxian Zhu
2024-01-02  9:57           ` Xi Ruoyao
     [not found]         ` <5f0f4c83-f6d8-4af3-8cce-e12cd5314da1@oss.cipunited.com>
2024-01-31  9:08           ` Xi Ruoyao
2024-01-25 13:58     ` Junxian Zhu
2024-01-25 14:37       ` Xi Ruoyao
2023-12-25 12:36   ` YunQiang Su
2023-12-26  2:48     ` Junxian Zhu
2024-01-02  9:51     ` Junxian Zhu
2023-12-29  1:00   ` Joseph Myers

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=20231225103548.1615-3-zhujunxian@oss.cipunited.com \
    --to=zhujunxian@oss.cipunited.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rongrong@oss.cipunited.com \
    /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: link
Be 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).