public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: "Alex Xu (Hello71) via Gcc-patches" <gcc-patches@gcc.gnu.org>,
	ibuclaw@gdcproject.org
Subject: Re: [PATCH 1/2] libphobos: fix CET for non-glibc targets
Date: Mon, 20 Dec 2021 10:41:09 -0500	[thread overview]
Message-ID: <1640012577.gxclos97ed.none@localhost> (raw)
In-Reply-To: <383024307.194459.1640008576821@office.mailbox.org>

Excerpts from ibuclaw@gdcproject.org's message of December 20, 2021 8:56 am:
>> On 20/12/2021 01:08 Alex Xu (Hello71) via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> 
>>  
>> On musl, linking against libphobos fails because it requires ucontext
>> but is not explicitly linked against it. This is caused by configure
>> assuming that it is implemented in assembly, but it is actually not
>> implemented. This silently works on other libcs because context API does
>> not require an external library.
> 
> Thanks.
> 
> Looks reasonable to me, also for backporting to gcc-11, which also has the same CET support.
> 
> Iain.
> 

Yes, we noticed this first on gcc 11. I tested that these patches fix 
the issue on gcc 11, and since nothing seems to have changed, I think 
the same problem exists and will be fixed by these patches on master.

Cheers,
Alex.

  reply	other threads:[~2021-12-20 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211220000831.332831-1-alex_y_xu.ref@yahoo.ca>
2021-12-20  0:08 ` Alex Xu (Hello71)
2021-12-20  0:08   ` [PATCH 2/2] libphobos: don't compile empty switchcontext.S Alex Xu (Hello71)
2021-12-20 13:56   ` [PATCH 1/2] libphobos: fix CET for non-glibc targets ibuclaw
2021-12-20 15:41     ` Alex Xu (Hello71) [this message]
2021-12-20 21:00       ` ibuclaw
2021-12-28 14:18         ` Alex Xu (Hello71)

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=1640012577.gxclos97ed.none@localhost \
    --to=alex_y_xu@yahoo.ca \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ibuclaw@gdcproject.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).