From: Andreas Schwab <schwab@suse.de>
To: Sergey Bugaev via Libc-alpha <libc-alpha@sourceware.org>
Cc: Sergey Bugaev <bugaevc@gmail.com>
Subject: Re: [RFC PATCH 1/6] Mark more functions as __COLD
Date: Mon, 15 May 2023 17:22:19 +0200 [thread overview]
Message-ID: <mvmjzx9k4b8.fsf@suse.de> (raw)
In-Reply-To: <20230515144815.3939017-2-bugaevc@gmail.com> (Sergey Bugaev via Libc-alpha's message of "Mon, 15 May 2023 17:48:10 +0300")
On Mai 15 2023, Sergey Bugaev via Libc-alpha wrote:
> diff --git a/include/stdio.h b/include/stdio.h
> index da47d1ce..b5257dd5 100644
> --- a/include/stdio.h
> +++ b/include/stdio.h
> @@ -171,9 +171,11 @@ extern int __gen_tempname (char *__tmpl, int __suffixlen, int __flags,
> /* Print out MESSAGE (which should end with a newline) on the error output
> and abort. */
> extern void __libc_fatal (const char *__message)
> - __attribute__ ((__noreturn__));
> -_Noreturn void __libc_message (const char *__fnt, ...) attribute_hidden;
> -extern void __fortify_fail (const char *msg) __attribute__ ((__noreturn__));
> + __attribute__ ((__noreturn__)) __COLD;
> +extern void __libc_message (const char *__fnt, ...)
> + attribute_hidden __attribute__ ((__noreturn__)) __COLD;
Any reason you replaced _Noreturn with __attribute__ ((__noreturn__))
here ...
> diff --git a/malloc/malloc.c b/malloc/malloc.c
> index 5d8b61d6..75e4eb2f 100644
> --- a/malloc/malloc.c
> +++ b/malloc/malloc.c
> @@ -1093,7 +1093,7 @@ static void* _int_memalign(mstate, size_t, size_t);
> static void* _mid_memalign(size_t, size_t, void *);
> #endif
>
> -static void malloc_printerr(const char *str) __attribute__ ((noreturn));
> +_Noreturn static void malloc_printerr(const char *str) __COLD;
... but did the other way here?
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-05-15 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:48 [RFC PATCH 0/6] .text.subsections for some questionable benefit Sergey Bugaev
2023-05-15 14:48 ` [RFC PATCH 1/6] Mark more functions as __COLD Sergey Bugaev
2023-05-15 15:22 ` Andreas Schwab [this message]
2023-05-15 15:27 ` Sergey Bugaev
2023-05-18 17:06 ` [PATCH v2] " Sergey Bugaev
2023-05-18 19:43 ` Adhemerval Zanella Netto
2023-05-19 10:35 ` Sergey Bugaev
2023-05-22 20:41 ` Adhemerval Zanella Netto
2023-05-15 14:48 ` [RFC PATCH 2/6] mcheck: Microoptimize Sergey Bugaev
2023-05-15 14:48 ` [RFC PATCH 3/6] sys/cdefs.h: Define __TEXT_STARTUP & __TEXT_EXIT Sergey Bugaev
2023-05-15 14:48 ` [RFC PATCH 4/6] Mark various functions as __TEXT_STARTUP and __TEXT_EXIT Sergey Bugaev
2023-05-15 14:48 ` [RFC PATCH 5/6] Also place entry points into .text.startup Sergey Bugaev
2023-05-15 14:48 ` [RFC PATCH 6/6] mach: In rtld, mark MIG routines as __TEXT_STARTUP Sergey Bugaev
2023-05-15 15:33 ` [RFC PATCH 0/6] .text.subsections for some questionable benefit Cristian Rodríguez
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=mvmjzx9k4b8.fsf@suse.de \
--to=schwab@suse.de \
--cc=bugaevc@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).