public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>, gcc-patches@gcc.gnu.org
Cc: nd@arm.com
Subject: Re: [PATCH v6] aarch64: Add split-stack support
Date: Thu, 15 Feb 2018 18:19:00 -0000	[thread overview]
Message-ID: <f9fe6d4a-521b-eae4-568a-be75249c3e30@linaro.org> (raw)
In-Reply-To: <675abb5d-c23f-cf4d-92d2-0c5ce4902628@arm.com>



On 13/02/2018 13:13, Szabolcs Nagy wrote:
> On 07/02/18 18:07, Adhemerval Zanella wrote:
>  5. The TCB support on GLIBC is meant to be included in version 2.28.
>>
> ...
>> +/* -fsplit-stack uses a TCB field available on glibc-2.27.  GLIBC also
>> +   exports symbol, __tcb_private_ss, to signal it has the field available
>> +   on TCB bloc.  This aims to prevent binaries linked against newer
>> +   GLIBC to run on non-supported ones.  */
> 
> 
> i suspect this needs to be updated since the glibc patch
> is not committed yet.
> 
> (i'll review the glibc patch, if it looks ok then it can
> be committed after the gcc side is accepted.)

I fixed the commit message locally, thanks for checking on this.

> 
>> +
>> +static bool
>> +aarch64_supports_split_stack (bool report ATTRIBUTE_UNUSED,
>> +                  struct gcc_options *opts ATTRIBUTE_UNUSED)
>> +{
>> +#ifndef TARGET_GLIBC_MAJOR
>> +#define TARGET_GLIBC_MAJOR 0
>> +#endif
>> +#ifndef TARGET_GLIBC_MINOR
>> +#define TARGET_GLIBC_MINOR 0
>> +#endif
>> +  /* Note: Can't test DEFAULT_ABI here, it isn't set until later.  */
>> +  if (TARGET_GLIBC_MAJOR * 1000 + TARGET_GLIBC_MINOR >= 2026)
>> +    return true;
>> +
>> +  if (report)
>> +    error ("%<-fsplit-stack%> currently only supported on AArch64 GNU/Linux with glibc-2.27 or later");
>> +  return false;
>> +}
>> +
>> +#undef TARGET_SUPPORTS_SPLIT_STACK
>> +#define TARGET_SUPPORTS_SPLIT_STACK aarch64_supports_split_stack
>> +

  reply	other threads:[~2018-02-15 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 18:07 Adhemerval Zanella
2018-02-13 15:13 ` Szabolcs Nagy
2018-02-15 18:19   ` Adhemerval Zanella [this message]
2018-02-27 13:44 ` Adhemerval Zanella
2018-02-13 16:40 Wilco Dijkstra

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=f9fe6d4a-521b-eae4-568a-be75249c3e30@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=szabolcs.nagy@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).