From: Jaydeep Patil <Jaydeep.Patil@imgtec.com>
To: "Rich Felker (dalias@libc.org)" <dalias@libc.org>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: RE: [PATCH] MIPS64 atomic_arch.h Clang complains about input type
Date: Tue, 8 Mar 2016 10:09:43 +0000 [thread overview]
Message-ID: <BD7773622145634B952E5B54ACA8E349AA245E9E@PUMAIL01.pu.imgtec.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Added musl@lists.openwall.com<mailto:musl@lists.openwall.com> in Cc
From: Jaydeep Patil
Sent: 08 March 2016 PM 03:38
To: Rich Felker (dalias@libc.org)
Subject: [PATCH] MIPS64 atomic_arch.h Clang complains about input type
Hi Rich,
Clang (3.9.0) generates following error for a_sc_p function in atomic_arch.h:
./arch/mips64/atomic_arch.h:37:29: error: unsupported inline asm: input with type 'long *' matching output with type 'int'
Could you please consider this patch to fix it?
-----
From 3e64da8f5db923a919cd5600e8031c158a0368a2 Mon Sep 17 00:00:00 2001
From: Jaydeep Patil <jaydeep.patil@imgtec.com>
Date: Tue, 8 Mar 2016 10:06:38 +0000
Subject: [PATCH] [MIPS64] Fix Clang error
---
arch/mips64/atomic_arch.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/mips64/atomic_arch.h b/arch/mips64/atomic_arch.h
index 49d9884..8af6500 100644
--- a/arch/mips64/atomic_arch.h
+++ b/arch/mips64/atomic_arch.h
@@ -29,9 +29,9 @@ static inline void *a_ll_p(volatile long *p)
}
#define a_sc_p a_sc_p
-static inline int a_sc_p(volatile long *p, void *v)
+static inline void *a_sc_p(volatile long *p, void *v)
{
- int r;
+ void *r;
__asm__ __volatile__ (
"scd %0, %1"
: "=r"(r), "=m"(*p) : "0"(v) : "memory");
--
2.1.4
Thanks,
Jaydeep
[-- Attachment #2: Type: text/html, Size: 6088 bytes --]
next reply other threads:[~2016-03-08 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 10:09 Jaydeep Patil [this message]
2016-03-08 11:26 ` Szabolcs Nagy
2016-03-08 17:26 ` Rich Felker (dalias@libc.org)
2016-03-08 18:11 ` Szabolcs Nagy
2016-03-09 5:00 Jaydeep Patil
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=BD7773622145634B952E5B54ACA8E349AA245E9E@PUMAIL01.pu.imgtec.org \
--to=jaydeep.patil@imgtec.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).