public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Use RAII in std::vector::_M_realloc_insert
Date: Wed, 28 Jun 2023 09:21:56 +0100	[thread overview]
Message-ID: <CACb0b4k=A9e-C-A4fcgd2PBcyuEdm2S6Vr0rsb7PxKAx0Sx3tg@mail.gmail.com> (raw)
In-Reply-To: <ZJvnnCVGxsZrbhtd@kam.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 6707 bytes --]

On Wed, 28 Jun 2023 at 08:56, Jan Hubicka wrote:

> > I think the __throw_bad_alloc() and __throw_bad_array_new_length()
> > functions should always be rare, so marking them cold seems fine (users
> who
> > define their own allocators that want to throw bad_alloc "often" will
> > probably throw it directly, they shouldn't be using our
> __throw_bad_alloc()
> > function anyway). I don't think __throw_bad_exception is ever used, so
> that
> > doesn't matter (we could remove it from the header and just keep its
> > definition in the library, but there's no big advantage to doing that).
> > Others like __throw_length_error() should also be very very rare, and
> could
> > be marked cold.
> >
> > Maybe we should just mark everything in <bits/functexcept.h> as cold. If
> > users want to avoid the cost of calls to those functions they can do so
> by
> > checking function preconditions/arguments to avoid the exceptions. There
> > are very few places where a throwing libstdc++ API doesn't have a way to
> > avoid the exception. The only one that isn't easily avoidable is
> > __throw_bad_alloc but OOM should be rare.
>
> Hi,
> this marks everything in functexcept.h as cold and I also noticed that
> we probably want to mark as such terminate.
>
> With fix to 110436 and -O3 we now inline _M_realloc_insert, yay :)
>
> tested on x86_64-linux, OK?
>

OK for trunk, thanks.


>
>         * include/bits/c++config (std::__terminate): Mark cold.
>         * include/bits/functexcept.h: Mark everything as cold.
>         * libsupc++/exception: Mark terminate and unexpected as cold.
> diff --git a/libstdc++-v3/include/bits/c++config
> b/libstdc++-v3/include/bits/c++config
> index 009a017b048..dd47f274d5f 100644
> --- a/libstdc++-v3/include/bits/c++config
> +++ b/libstdc++-v3/include/bits/c++config
> @@ -320,7 +320,7 @@ namespace std
>    extern "C++" __attribute__ ((__noreturn__, __always_inline__))
>    inline void __terminate() _GLIBCXX_USE_NOEXCEPT
>    {
> -    void terminate() _GLIBCXX_USE_NOEXCEPT __attribute__ ((__noreturn__));
> +    void terminate() _GLIBCXX_USE_NOEXCEPT __attribute__
> ((__noreturn__,__cold__));
>      terminate();
>    }
>  #pragma GCC visibility pop
> diff --git a/libstdc++-v3/include/bits/functexcept.h
> b/libstdc++-v3/include/bits/functexcept.h
> index 2765f7865df..a2e97413661 100644
> --- a/libstdc++-v3/include/bits/functexcept.h
> +++ b/libstdc++-v3/include/bits/functexcept.h
> @@ -57,61 +57,61 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
>
>    // Helper for exception objects in <typeinfo>
>    void
> -  __throw_bad_cast(void) __attribute__((__noreturn__));
> +  __throw_bad_cast(void) __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_bad_typeid(void) __attribute__((__noreturn__));
> +  __throw_bad_typeid(void) __attribute__((__noreturn__,__cold__));
>
>    // Helpers for exception objects in <stdexcept>
>    void
> -  __throw_logic_error(const char*) __attribute__((__noreturn__));
> +  __throw_logic_error(const char*) __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_domain_error(const char*) __attribute__((__noreturn__));
> +  __throw_domain_error(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_invalid_argument(const char*) __attribute__((__noreturn__));
> +  __throw_invalid_argument(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_length_error(const char*) __attribute__((__noreturn__));
> +  __throw_length_error(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_out_of_range(const char*) __attribute__((__noreturn__));
> +  __throw_out_of_range(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_out_of_range_fmt(const char*, ...) __attribute__((__noreturn__))
> +  __throw_out_of_range_fmt(const char*, ...)
> __attribute__((__noreturn__,__cold__))
>      __attribute__((__format__(__gnu_printf__, 1, 2)));
>
>    void
> -  __throw_runtime_error(const char*) __attribute__((__noreturn__));
> +  __throw_runtime_error(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_range_error(const char*) __attribute__((__noreturn__));
> +  __throw_range_error(const char*) __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_overflow_error(const char*) __attribute__((__noreturn__));
> +  __throw_overflow_error(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_underflow_error(const char*) __attribute__((__noreturn__));
> +  __throw_underflow_error(const char*)
> __attribute__((__noreturn__,__cold__));
>
>    // Helpers for exception objects in <ios>
>    void
> -  __throw_ios_failure(const char*) __attribute__((__noreturn__));
> +  __throw_ios_failure(const char*) __attribute__((__noreturn__,__cold__));
>
>    void
> -  __throw_ios_failure(const char*, int) __attribute__((__noreturn__));
> +  __throw_ios_failure(const char*, int)
> __attribute__((__noreturn__,__cold__));
>
>    // Helpers for exception objects in <system_error>
>    void
> -  __throw_system_error(int) __attribute__((__noreturn__));
> +  __throw_system_error(int) __attribute__((__noreturn__,__cold__));
>
>    // Helpers for exception objects in <future>
>    void
> -  __throw_future_error(int) __attribute__((__noreturn__));
> +  __throw_future_error(int) __attribute__((__noreturn__,__cold__));
>
>    // Helpers for exception objects in <functional>
>    void
> -  __throw_bad_function_call() __attribute__((__noreturn__));
> +  __throw_bad_function_call() __attribute__((__noreturn__,__cold__));
>
>  #else // ! HOSTED
>
> diff --git a/libstdc++-v3/libsupc++/exception
> b/libstdc++-v3/libsupc++/exception
> index a34386e6026..00a6347ebe5 100644
> --- a/libstdc++-v3/libsupc++/exception
> +++ b/libstdc++-v3/libsupc++/exception
> @@ -75,7 +75,7 @@ namespace std _GLIBCXX_VISIBILITY(default)
>
>    /** The runtime will call this function if %exception handling must be
>     *  abandoned for any reason.  It can also be called by the user.  */
> -  void terminate() _GLIBCXX_USE_NOEXCEPT __attribute__ ((__noreturn__));
> +  void terminate() _GLIBCXX_USE_NOEXCEPT __attribute__
> ((__noreturn__,__cold__));
>
>  #if __cplusplus < 201703L || (__cplusplus <= 202002L &&
> _GLIBCXX_USE_DEPRECATED)
>    /// If you write a replacement %unexpected handler, it must be of this
> type.
> @@ -104,7 +104,7 @@ namespace std _GLIBCXX_VISIBILITY(default)
>     * @deprecated Removed from the C++ standard in C++17
>     */
>    _GLIBCXX11_DEPRECATED
> -  void unexpected() __attribute__ ((__noreturn__));
> +  void unexpected() __attribute__ ((__noreturn__,__cold__));
>  #endif
>
>    /** [18.6.4]/1:  'Returns true after completing evaluation of a
>
>

  reply	other threads:[~2023-06-28  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 13:38 Jonathan Wakely
2023-06-23 16:44 ` Jan Hubicka
2023-06-23 18:19   ` Jonathan Wakely
2023-06-28  7:56     ` Jan Hubicka
2023-06-28  8:21       ` Jonathan Wakely [this message]
2023-07-10 12:53       ` Jonathan Wakely

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='CACb0b4k=A9e-C-A4fcgd2PBcyuEdm2S6Vr0rsb7PxKAx0Sx3tg@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=libstdc++@gcc.gnu.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).