public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: odd endianness toolchains for crosstool
Date: Mon, 25 Apr 2022 19:20:56 +0200	[thread overview]
Message-ID: <YmbYeGNhNKdMgidP@zx2c4.com> (raw)
In-Reply-To: <YmbUBZg/nGV7gLyy@zx2c4.com>

On Mon, Apr 25, 2022 at 07:01:57PM +0200, Jason A. Donenfeld wrote:
> For ppc32? I'm unable to produce working executables with the toolchain.
> And looking at the target info, -msecure-plt is missing, while
> -mlong-double-64 is there:
> 
> $ ./powerpc-linux-gcc -Q --help=target | grep long-double
>   -mlong-double-                        64
> $ ./powerpc-linux-gcc -Q --help=target | grep msecure-plt
>   -msecure-plt                          [disabled]

And looking at the actual sections of the binary, indeed the .plt
section is RWX, which means it's not getting -msecure-plt as it should.

  reply	other threads:[~2022-04-25 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  1:39 odd endianness toolchains for crosstool Jason A. Donenfeld
2022-04-25  8:46 ` Arnd Bergmann
2022-04-25 11:43   ` Jason A. Donenfeld
2022-04-25 14:55     ` Arnd Bergmann
2022-04-25 15:20       ` Jason A. Donenfeld
2022-04-25 15:39         ` Arnd Bergmann
2022-04-25 15:53           ` Jason A. Donenfeld
2022-04-25 16:15             ` Arnd Bergmann
2022-04-25 17:01               ` Jason A. Donenfeld
2022-04-25 17:20                 ` Jason A. Donenfeld [this message]
2022-04-25 17:40                 ` Arnd Bergmann
2022-04-25 17:42                   ` Jason A. Donenfeld
2022-04-28  6:43 ` Rob Landley
2024-08-29 15:51 ` Jason A. Donenfeld
2024-08-29 20:25   ` Arnd Bergmann
2024-09-03  1:23     ` Nathan Chancellor
2024-09-03  6:59       ` Arnd Bergmann

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=YmbYeGNhNKdMgidP@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox