From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: [COMMITTED 2/8] debug: Reformat Makefile.
Date: Tue, 16 May 2023 08:48:18 -0400 [thread overview]
Message-ID: <20230516124824.146416-3-carlos@redhat.com> (raw)
In-Reply-To: <20230516124824.146416-1-carlos@redhat.com>
Fix list terminator whitspace.
Sort using scripts/sort-makefile-lines.py.
No code generation changes observed in binary artifacts.
No regressions on x86_64 and i686.
---
debug/Makefile | 34 ++++++++++++++++++----------------
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/debug/Makefile b/debug/Makefile
index a8b4036cdc..096df27aeb 100644
--- a/debug/Makefile
+++ b/debug/Makefile
@@ -29,6 +29,7 @@ headers := execinfo.h
# login/Makefile instead. If that subdir is omitted from the
# build, its _FORTIFY_SOURCE support will be too.
routines = \
+ $(static-only-routines) \
____longjmp_chk \
asprintf_chk \
backtrace \
@@ -113,7 +114,6 @@ routines = \
wmempcpy_chk \
wmemset_chk \
wprintf_chk \
- $(static-only-routines) \
# routines
static-only-routines := stack_chk_fail_local
@@ -267,23 +267,25 @@ CFLAGS-tst-ssp-1.c += -fstack-protector-all
CFLAGS-tst-sprintf-fortify-unchecked.c = \
-fno-builtin-vsprintf -fno-builtin-__vsprintf_chk
-tests = backtrace-tst \
- tst-longjmp_chk \
- test-strcpy_chk \
- test-stpcpy_chk \
- tst-longjmp_chk2 \
- tst-backtrace2 \
- tst-backtrace3 \
- tst-backtrace4 \
- tst-backtrace5 \
- tst-backtrace6 \
- tst-realpath-chk \
- tst-sprintf-fortify-unchecked \
- $(tests-all-chk)
+tests = \
+ $(tests-all-chk) \
+ backtrace-tst \
+ test-stpcpy_chk \
+ test-strcpy_chk \
+ tst-backtrace2 \
+ tst-backtrace3 \
+ tst-backtrace4 \
+ tst-backtrace5 \
+ tst-backtrace6 \
+ tst-longjmp_chk \
+ tst-longjmp_chk2 \
+ tst-realpath-chk \
+ tst-sprintf-fortify-unchecked \
+ # tests
tests-time64 += \
- $(tests-all-time64-chk) \
- # tests-time64
+ $(tests-all-time64-chk) \
+ # tests-time64
ifeq ($(have-ssp),yes)
tests += tst-ssp-1
--
2.40.0
next prev parent reply other threads:[~2023-05-16 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:48 [COMMITTED 0/8] Reformat most used Makefiles Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 1/8] elf: Reformat Makefile Carlos O'Donell
2023-05-16 12:48 ` Carlos O'Donell [this message]
2023-05-16 12:48 ` [COMMITTED 3/8] misc: " Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 4/8] socket: " Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 5/8] stdio-common: " Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 6/8] stdlib: " Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 7/8] linux: " Carlos O'Donell
2023-05-16 12:48 ` [COMMITTED 8/8] wcsmbs: " Carlos O'Donell
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=20230516124824.146416-3-carlos@redhat.com \
--to=carlos@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).