From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Sanders <daniel.sanders@imgtec.com>
Cc: linux-mips@linux-mips.org, Paul Burton <paul.burton@imgtec.com>,
Markos Chandras <markos.chandras@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
Behan Webster <behanw@converseincode.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
David Daney <ddaney.cavm@gmail.com>
Subject: Re: [PATCH v2] MIPS: Changed current_thread_info() to an equivalent supported by both clang and GCC
Date: Fri, 16 Jan 2015 15:47:04 +0100 [thread overview]
Message-ID: <20150116144703.GC22296@linux-mips.org> (raw)
In-Reply-To: <1420894360-13479-1-git-send-email-daniel.sanders@imgtec.com>
On Sat, Jan 10, 2015 at 12:52:40PM +0000, Daniel Sanders wrote:
> The problem is that clang doesn't honour named registers on local variables
> and silently treats them as normal uninitialized variables. However, it
> does honour them on global variables.
Older versions of <asm/unistd.h> which have been copied into some userland
packages are using some local register variables in syscall wrappers. These
syscall wrappers have historically been a pain because every once in a
while they got broken by a new GCC release or other issues. If you're
lucky that has been resolved by the maintainers of those external software
packages - the only way to be certain is the review ...
At least the kernel does no longer do syscalls.
Ralf
next prev parent reply other threads:[~2015-01-16 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 12:52 [PATCH v2] MIPS: Changed current_thread_info() to an equivalent supported by both clang and GCC Daniel Sanders
2015-01-10 12:52 ` Daniel Sanders
2015-01-16 14:47 ` Ralf Baechle [this message]
2015-01-17 15:52 ` Daniel Sanders
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=20150116144703.GC22296@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=behanw@converseincode.com \
--cc=daniel.sanders@imgtec.com \
--cc=ddaney.cavm@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=sergei.shtylyov@cogentembedded.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