public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] <shlib-compat.h>: Support compat_symbol_reference for _ISOMAC
Date: Tue, 02 Mar 2021 22:26:14 +0100	[thread overview]
Message-ID: <87pn0hw8ll.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOqH=wqnx-XrV+ndtZGmqKRgSdCH-zwc85SYBwTNH97zRQ@mail.gmail.com> (H. J. Lu's message of "Tue, 2 Mar 2021 13:18:21 -0800")

* H. J. Lu:

> On Tue, Mar 2, 2021 at 1:02 PM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> * H. J. Lu:
>>
>> > On Tue, Mar 2, 2021 at 12:10 PM Florian Weimer via Libc-alpha
>> > <libc-alpha@sourceware.org> wrote:
>> >>
>> >> This is helpful for testing compat symbols in cases where _ISOMAC
>> >> is activated implicitly due to -DMODULE_NAME=testsuite and cannot
>> >> be disabled easily.
>> >>
>> >> ---
>> >> v2: Now actually tested in the situation where I need it.
>> >>
>> >
>> > Any particular tests which need this?
>>
>> nptl/tst-cleanup4aux.c will need this once _pthread_cleanup_push,
>> _pthread_cleanup_pop are compatibility symbols.

> Do you just want to link against the older version and nothing else?

It's the only version, but yes.

Thanks,
Florian


  parent reply	other threads:[~2021-03-02 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 19:30 Florian Weimer
2021-03-02 20:44 ` H.J. Lu
2021-03-02 21:02   ` Florian Weimer
2021-03-02 21:18     ` H.J. Lu
2021-03-02 21:23       ` H.J. Lu
2021-03-02 21:28         ` Florian Weimer
2021-03-02 21:33           ` H.J. Lu
2021-03-02 21:35             ` Florian Weimer
2021-03-03 10:04               ` Florian Weimer
2021-03-05 13:06             ` Florian Weimer
2021-03-02 21:26       ` Florian Weimer [this message]
2021-03-03  8:39 ` Andreas Schwab
2021-03-03  8:53   ` Florian Weimer

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=87pn0hw8ll.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=hjl.tools@gmail.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).