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 3/7] elf: Split dl-printf.c from dl-misc.c
Date: Fri, 14 Jan 2022 15:27:38 +0100	[thread overview]
Message-ID: <87lezitmsl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOoFU4H6aJXjaF9AExSpDO5-2hj_3kGzTUmLMmgLimcR2A@mail.gmail.com> (H. J. Lu's message of "Fri, 14 Jan 2022 06:25:39 -0800")

* H. J. Lu:

> On Fri, Jan 14, 2022 at 4:42 AM Florian Weimer via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>> This allows to use different compiler flags for the diagnostics
>> code.
>> ---
>>  elf/Makefile    |   2 +-
>>  elf/dl-misc.c   | 281 +---------------------------------------------
>>  elf/dl-printf.c | 292 ++++++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 297 insertions(+), 278 deletions(-)
>>  create mode 100644 elf/dl-printf.c
>>
>> diff --git a/elf/Makefile b/elf/Makefile
>> index b86d116be9..0c4be43deb 100644
>> --- a/elf/Makefile
>> +++ b/elf/Makefile
>> @@ -31,7 +31,7 @@ routines      = $(all-dl-routines) dl-support dl-iteratephdr \
>>  # The core dynamic linking functions are in libc for the static and
>>  # profiled libraries.
>>  dl-routines    = $(addprefix dl-,load lookup object reloc deps \
>> -                                 runtime init fini debug misc \
>> +                                 runtime init fini debug misc printf \
>>                                   version profile tls origin scope \
>>                                   execstack open close trampoline \
>>                                   exception sort-maps lookup-direct \
>
> Should we put one item per-line now?

And drop the addprefix?  I can submit a separate patch for that.

Thanks,
Florian


  reply	other threads:[~2022-01-14 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 12:40 [PATCH 0/7] Reliable CPU compatibility diagnostics in ld.so Florian Weimer
2022-01-14 12:40 ` [PATCH 1/7] x86: HAVE_X86_LAHF_SAHF, HAVE_X86_MOVBE and -march=x86-64-vN (bug 28782) Florian Weimer
2022-01-14 14:21   ` H.J. Lu
2022-01-14 12:40 ` [PATCH 2/7] Generate gcc-macros.h Florian Weimer
2022-01-14 14:24   ` H.J. Lu
2022-01-14 12:40 ` [PATCH 3/7] elf: Split dl-printf.c from dl-misc.c Florian Weimer
2022-01-14 14:25   ` H.J. Lu
2022-01-14 14:27     ` Florian Weimer [this message]
2022-01-14 14:32       ` H.J. Lu
2022-01-14 12:40 ` [PATCH 4/7] Add --early-cflags configure option Florian Weimer
2022-01-14 14:27   ` H.J. Lu
2022-01-14 14:29     ` Florian Weimer
2022-01-14 14:33       ` H.J. Lu
2022-01-14 14:34         ` Florian Weimer
2022-01-14 12:40 ` [PATCH 5/7] powerpc64le: Use <gcc-macros.h> in early HWCAP check Florian Weimer
2022-01-14 12:41 ` [PATCH 6/7] x86: Add x86-64-vN check to early startup Florian Weimer
2022-01-14 12:41 ` [PATCH 7/7] s390x: Use <gcc-macros.h> in early HWCAP check Florian Weimer
2022-01-18 12:42   ` Stefan Liebler
2022-01-18 12:54     ` Florian Weimer
2022-01-18 13:31       ` Stefan Liebler
2022-01-18 13:33         ` Florian Weimer
2022-01-18 13:38           ` Stefan Liebler
2022-01-18 21:03             ` Joseph Myers
2022-01-18 21:21               ` 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=87lezitmsl.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).