From: Christopher Friedt <chrisfriedt@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Cortex-M support
Date: Wed, 12 Sep 2018 20:41:15 -0400 [thread overview]
Message-ID: <CAF4BF-QZLOq2AMygBJJqottxZX2c=Wd1-aafj4s-cozo-3SMtQ@mail.gmail.com> (raw)
In-Reply-To: <36bbe45c-c96b-94ae-5249-70eae56aab31@phoenixsoftware.it>
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
It does :) Although only through thumbv2, so there would be some assembly
rework required for cortex-m0.
On Wed., Sep. 12, 2018, 8:39 p.m. Pierluigi Passaro, <
pierluigi.passaro@phoenixsoftware.it> wrote:
> Hi,
> I was wondering if musl already supports Cortex-M or not.
> Thanks
> Regards
> Pier
>
[-- Attachment #2: Type: text/html, Size: 574 bytes --]
next prev parent reply other threads:[~2018-09-13 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 0:39 Pierluigi Passaro
2018-09-13 0:41 ` Christopher Friedt [this message]
2018-09-13 0:52 ` Rich Felker
2018-09-13 1:06 ` Pierluigi Passaro
2018-09-13 1:24 ` Rich Felker
2018-09-13 9:43 ` Szabolcs Nagy
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='CAF4BF-QZLOq2AMygBJJqottxZX2c=Wd1-aafj4s-cozo-3SMtQ@mail.gmail.com' \
--to=chrisfriedt@gmail.com \
--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).