From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't run personality syscall at configure time; don't check it at all
Date: Fri, 07 May 2021 08:13:26 -0600 [thread overview]
Message-ID: <875yzupr7d.fsf@tromey.com> (raw)
In-Reply-To: <20210506224341.398202-1-pedro@palves.net> (Pedro Alves's message of "Thu, 6 May 2021 23:43:41 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> Since HAVE_PERSONALITY is only checked in Linux code, and
Pedro> ADDR_NO_RANDOMIZE exists for over 15 years, I propose just completely
Pedro> removing the configure checks.
Seems fine to me. Thank you.
Pedro> If for some odd reason, some remotely modern system still needs a
Pedro> configure check, then we can revert this commit but drop the
Pedro> AC_RUN_IFELSE in favor of always doing the AC_LINK_IFELSE
Pedro> cross-compile fallback.
Also makes sense.
Tom
next prev parent reply other threads:[~2021-05-07 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 22:43 Pedro Alves
2021-05-07 14:13 ` Tom Tromey [this message]
2021-05-07 17:42 ` Lancelot SIX via Gdb-patches
2021-05-08 12:11 ` [pushed] Don't include sys/personality.h in linux-low.cc anymore Pedro Alves
2021-05-12 18:24 ` [PATCH] Don't run personality syscall at configure time; don't check it at all Tom Tromey
2021-05-12 19:56 ` Pedro Alves
2021-05-12 19:58 ` Tom Tromey
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=875yzupr7d.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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