From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id 99608211FF for ; Thu, 15 Feb 2024 10:19:01 +0100 (CET) Received: (qmail 27805 invoked by uid 550); 15 Feb 2024 09:15:54 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 27773 invoked from network); 15 Feb 2024 09:15:54 -0000 Date: Thu, 15 Feb 2024 10:18:47 +0100 From: Szabolcs Nagy To: enh Cc: Rich Felker , William Roberts , musl@lists.openwall.com Message-ID: <20240215091847.GB1884416@port70.net> Mail-Followup-To: enh , Rich Felker , William Roberts , musl@lists.openwall.com References: <20240212184236.GZ4163@brightrain.aerifal.cx> <20240212224657.GA4163@brightrain.aerifal.cx> <20240213020834.GB4163@brightrain.aerifal.cx> <20240215000353.GA1884416@port70.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: Subject: Re: [musl] PAC/BTI Support on aarch64 * enh [2024-02-14 16:22:05 -0800]: > On Wed, Feb 14, 2024 at 4:03=E2=80=AFPM Szabolcs Nagy wr= ote: > > i.e. no equivalent to -Wa,--noexecstack we use for GNU_STACK > > (this was an oversight, llvm added an option, binutils gas has none). >=20 > 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= =2Ehtml#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. >=20 > 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