From: Michael Ellerman <mpe@ellerman•id.au>
To: Anton Blanchard <anton@samba•org>
Cc: paulus@samba•org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] powerpc: 32 bit getcpu VDSO function uses 64 bit instructions
Date: Thu, 27 Nov 2014 09:38:17 +1100 [thread overview]
Message-ID: <1417041497.12952.2.camel@concordia> (raw)
In-Reply-To: <1417036288-22079-1-git-send-email-anton@samba.org>
On Thu, 2014-11-27 at 08:11 +1100, Anton Blanchard wrote:
> I used some 64 bit instructions when adding the 32 bit getcpu VDSO
> function. Fix it.
Ouch. The symptom is a SIGILL I presume?
Could we catch this by forcing -m32 in the CFLAGS for vdso32 ?
cheers
next prev parent reply other threads:[~2014-11-26 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 21:11 [PATCH] powerpc: 32 bit getcpu VDSO function uses 64 bit instructions Anton Blanchard
2014-11-26 22:38 ` Michael Ellerman [this message]
2014-11-26 23:23 ` Segher Boessenkool
2014-11-26 23:28 ` Segher Boessenkool
2014-11-26 23:50 ` Peter Bergner
2014-11-27 16:08 ` Segher Boessenkool
2014-11-27 17:41 ` Peter Bergner
2014-11-27 20:50 ` Segher Boessenkool
2014-11-28 2:00 ` Benjamin Herrenschmidt
2014-11-27 18:20 ` Andreas Schwab
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=1417041497.12952.2.camel@concordia \
--to=mpe@ellerman$(echo .)id.au \
--cc=anton@samba$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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