From: mzoran@crowfest.net (Michael Zoran)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: Disabling warnings about deprecated armv8 instructions
Date: Sun, 22 Jan 2017 06:02:40 -0800 [thread overview]
Message-ID: <1485093760.1494.2.camel@crowfest.net> (raw)
In-Reply-To: <0D1F678D-6F94-4B68-955E-6454F8647FCA@linaro.org>
On Sun, 2017-01-22 at 13:01 +0000, Ard Biesheuvel wrote:
> > On 22 Jan 2017, at 12:21, Michael Zoran <mzoran@crowfest.net>
> > wrote:
>
> > 2. Detect the binary type to detectermine if it should be silenced.
>
> The controls are system wide, not per process. And I think the
> somewhat unconventional requirement to run a v6 compatible userland
> justifies adding a line to the boot script that simply disarms all
> the deprecation warnings.
>
It depends on the point of view of the arm architecture. One point
of view if that if you have a new 64 bit application with access to
more feature, it has to be compiled with new instructions so no reason
to have the old around. But if you have an old 32 bit application,
then it keeps working.
> Any political differences in the rpi project regarding support of the
> 64 bit kernel are not upstream's problem imo
>
I am in no way associated with the rpi project or the organization.
I receive absolutely nothing from them and they are not supporting 64
bit at all other then as a hobbiest/experimental project.
I'm just a very interested enthusiast with a bit of time on my hand
now that finds 64 bit interesting. I found the idea of getting 32 bit
Raspbian to work as interesting.
> >
>
> I wonder why Mathematica cares about the personality. If it makes
> inferences about the architecture level to decide which instructions
> to use, it is clearly abusing the facility. Any clue?
>
No idea really. It may have something to do with licensing
requirements since it's targeted for education. In the sake of not
stepping on any toes I have no intention of submitting any patches or
changes to the personality because of that.
The personality issue is more an arm architcture issue and I am
quickly seeing is beyond the scope of what I'm trying to accomplish.
next prev parent reply other threads:[~2017-01-22 14:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 8:07 ARM64: Disabling warnings about deprecated armv8 instructions Michael Zoran
2017-01-22 8:52 ` Alexander Stein
2017-01-22 8:58 ` Michael Zoran
2017-01-22 9:05 ` Jisheng Zhang
2017-01-22 9:38 ` Michael Zoran
2017-01-22 9:43 ` Ard Biesheuvel
2017-01-22 9:52 ` Michael Zoran
2017-01-22 9:56 ` Michael Zoran
2017-01-22 10:54 ` Ard Biesheuvel
2017-01-22 11:05 ` Michael Zoran
2017-01-22 11:22 ` Michael Zoran
2017-01-22 9:09 ` Ard Biesheuvel
2017-01-22 9:33 ` Michael Zoran
2017-01-22 9:36 ` Ard Biesheuvel
2017-01-22 9:49 ` Michael Zoran
2017-01-22 11:46 ` Alexander Stein
2017-01-22 12:21 ` Michael Zoran
2017-01-22 13:01 ` Ard Biesheuvel
2017-01-22 14:02 ` Michael Zoran [this message]
2017-01-22 15:05 ` Ard Biesheuvel
2017-01-30 14:13 ` Russell King - ARM Linux
2017-01-30 14:50 ` Ard Biesheuvel
2017-01-30 16:38 ` Måns Rullgård
2017-01-30 16:58 ` Russell King - ARM Linux
2017-01-30 17:09 ` Ard Biesheuvel
2017-01-30 17:39 ` Eric Anholt
2017-01-30 17:41 ` Michael Zoran
2017-01-30 18:17 ` Måns Rullgård
2017-01-30 18:34 ` Michael Zoran
2017-01-30 18:49 ` Will Deacon
2017-01-30 19:53 ` Michael Zoran
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=1485093760.1494.2.camel@crowfest.net \
--to=mzoran@crowfest.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.