From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: PING^2: [PATCH 0/2] nptl: Update struct pthread_unwind_buf
Date: Wed, 21 Feb 2018 07:33:37 -0800 [thread overview]
Message-ID: <CAMe9rOpoaaL=2B6cjLcGdPtwtWUFp5Sd+St4i1rA+eq5c30wnw@mail.gmail.com> (raw)
On Thu, Feb 15, 2018 at 12:02 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Fri, Feb 9, 2018 at 7:24 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> On Fri, Feb 9, 2018 at 6:33 AM, Florian Weimer <fweimer@redhat.com> wrote:
>>> On 02/09/2018 03:13 PM, H.J. Lu wrote:
>>>>
>>>> I built glibc master with gcc-8.0.1 -mcet -fcf-protection. Some object
>>>> files do get CET marker as expected. But static executable isn't:
>>>
>>>
>>> I said static libraries. If I compile this code (based on the example from
>>> the manual page) on Fedora rawhide:
>>>
>>
>> Glibc never provides binary compatibility with static libraries. My suggestions
>> are
>>
>> 1. Recompile static libraries after CET is enabled in glibc. Or
>> 2. Don't compile static libraries with CET.
>>
>> BTW, we don't have space to save shadow stack register with existing
>> cancel buf.
>>
>
> PING:
>
> https://sourceware.org/ml/libc-alpha/2018-02/msg00290.html
> https://sourceware.org/ml/libc-alpha/2018-02/msg00291.html
>
PING.
--
H.J.
next reply other threads:[~2018-02-21 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 15:33 H.J. Lu [this message]
2018-02-24 5:48 ` PING^2: [PATCH 0/2] nptl: Update struct pthread_unwind_buf Carlos O'Donell
2018-02-24 15:20 ` H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOpoaaL=2B6cjLcGdPtwtWUFp5Sd+St4i1rA+eq5c30wnw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).