mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: enh <enh@google.com>
Cc: Rich Felker <dalias@libc.org>,
	William Roberts <bill.c.roberts@gmail.com>,
	musl@lists.openwall.com
Subject: Re: [musl] PAC/BTI Support on aarch64
Date: Thu, 15 Feb 2024 10:18:47 +0100	[thread overview]
Message-ID: <20240215091847.GB1884416@port70.net> (raw)
In-Reply-To: <CAJgzZopv1Pap2MHZ7-+3M8+4XE_RVsR8_kRa1=2fEcpXHtSBaw@mail.gmail.com>

* enh <enh@google.com> [2024-02-14 16:22:05 -0800]:
> On Wed, Feb 14, 2024 at 4:03 PM Szabolcs Nagy <nsz@port70.net> wrote:
> > i.e. no equivalent to -Wa,--noexecstack we use for GNU_STACK
> > (this was an oversight, llvm added an option, binutils gas has none).
> 
> what's the option? (since Android only supports llvm, that might be
> worth considering as a slight cleanup for us...)

-mmark-bti-property
https://releases.llvm.org/16.0.0/tools/clang/docs/ClangCommandLineReference.html#cmdoption-clang-mmark-bti-property
https://reviews.llvm.org/D81930

> > as far as i know openssl is the reason android does not enable pac:
> > they added the hint instructions incorrectly at first so there are
> > binaries that fail if the hw enables pac.
> 
> that was one reason why "android does not enable pac" _by default in
> the android target triples for app developers_, yes --- though i think
> we're at the point where we think we should flip that default (not
> least because the number of users whose devices would actually
> _benefit_ from the extra instructions is a lot larger now!):
> https://github.com/android/ndk/issues/1914

i see

  reply	other threads:[~2024-02-15  9:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 16:38 William Roberts
2024-02-12 18:42 ` Rich Felker
2024-02-12 21:25   ` William Roberts
2024-02-12 21:34     ` enh
2024-02-12 22:46     ` Rich Felker
2024-02-12 23:05       ` enh
2024-02-12 23:18         ` William Roberts
2024-02-13  2:08           ` Rich Felker
2024-02-13 14:47             ` William Roberts
2024-02-13 17:51               ` Markus Wichmann
2024-02-14  2:19                 ` Rich Felker
2024-02-14  3:19                   ` William Roberts
2024-02-14  4:44                   ` Markus Wichmann
2024-02-14 13:32                     ` Thorsten Glaser
2024-02-14 14:03                       ` Rich Felker
2024-02-14 14:12                         ` Thorsten Glaser
2024-02-15 13:29                   ` Stefan O'Rear
2024-02-15 14:06                     ` Rich Felker
2024-03-02 14:33                       ` Szabolcs Nagy
2024-03-02 14:45                         ` Rich Felker
2024-02-15  0:03             ` Szabolcs Nagy
2024-02-15  0:22               ` enh
2024-02-15  9:18                 ` Szabolcs Nagy [this message]
2024-02-19 23:54   ` Fangrui Song
     [not found]   ` <DS7PR12MB57659BC5D5536574D1B91D26CB502@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-02-20  6:21     ` Anton Korobeynikov

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=20240215091847.GB1884416@port70.net \
    --to=nsz@port70.net \
    --cc=bill.c.roberts@gmail.com \
    --cc=dalias@libc.org \
    --cc=enh@google.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).