mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Daniel Gutson <danielgutson@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Intel CET Support
Date: Tue, 25 May 2021 21:12:01 -0300	[thread overview]
Message-ID: <CAFdMc-1rLPk2H0Pq5o7HQRd0XTWCxm8CrhwaSHkALaM2jxDHLw@mail.gmail.com> (raw)
In-Reply-To: <41b3220c-630d-dba8-d8fb-6ffdce3514f1@overdrivepizza.com>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

El mar., 25 may. 2021 8:00 p. m., Joao Moreira <joao@overdrivepizza.com>
escribió:

> Hi,
>
> Long ago I sent some patches here to enable CET support within MUSL
> (https://www.openwall.com/lists/musl/2020/10/19/3).
>

Did you intentionally remove the : in the label?
If not, does this assembly without errors? How did you test this?

@@ -49,7 +52,8 @@ feclearexcept:

 .global feraiseexcept
 .type feraiseexcept,@function
-feraiseexcept:	
+feraiseexcept
+	ENDBRANCH32




> These patches were a result from some experiment I have been running
> with clang, and to which I needed a suitable library. I understand that
> the patches were not in their best shape, and I was a bit busy at the
> time so I didn't really push this through.
>
> Either way, I'm now wondering if there is any interest from MUSL to
> support CET. If yes, I can start working on an updated patch-set to be
> sent here eventually.
>
> Additionally, if the support is of interest, it would also be
> interesting to know if MUSL intends to support CET as specified in the
> X86-64 ABI (where a single linked DSO without the CET bits set disables
> the  feature) or if you have something different in mind.
>
> Tks,
> Joao.
>

[-- Attachment #2: Type: text/html, Size: 2046 bytes --]

  reply	other threads:[~2021-05-26  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 23:00 Joao Moreira
2021-05-26  0:12 ` Daniel Gutson [this message]
2021-05-26  1:07   ` Joao Moreira
2023-09-15  7:45 ` Sören Tempel
2023-09-16 19:14   ` 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=CAFdMc-1rLPk2H0Pq5o7HQRd0XTWCxm8CrhwaSHkALaM2jxDHLw@mail.gmail.com \
    --to=danielgutson@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).