public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] libstdc++: Fix the return type of __cxa_finalize
Date: Tue, 19 May 2020 09:08:56 +0000 (GMT)	[thread overview]
Message-ID: <20200519090856.93F6F397A4AE@sourceware.org> (raw)

https://gcc.gnu.org/g:1405ed433443c7df22364ef8c6574bbf9b10b61a

commit 1405ed433443c7df22364ef8c6574bbf9b10b61a
Author: Fangrui Song <maskray@google.com>
Date:   Mon May 4 23:07:19 2020 +0100

    libstdc++: Fix the return type of __cxa_finalize
    
    This should return void according to the Itanium C++ ABI.
    
    2020-05-04  Fangrui Song  <maskray@google.com>
    
            * libsupc++/cxxabi.h (__cxa_finalize): Fix return type.

Diff:
---
 libstdc++-v3/ChangeLog          | 4 ++++
 libstdc++-v3/libsupc++/cxxabi.h | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index a011ec5f45a..f4839debf76 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,7 @@
+2020-05-04  Fangrui Song  <maskray@google.com>
+
+	* libsupc++/cxxabi.h (__cxa_finalize): Fix return type.
+
 2020-05-04  Jonathan Wakely  <jwakely@redhat.com>
 
 	* doc/xml/faq.xml: Use working link for SGI STL FAQ.
diff --git a/libstdc++-v3/libsupc++/cxxabi.h b/libstdc++-v3/libsupc++/cxxabi.h
index 50298205daa..000713ecdf8 100644
--- a/libstdc++-v3/libsupc++/cxxabi.h
+++ b/libstdc++-v3/libsupc++/cxxabi.h
@@ -127,7 +127,7 @@ namespace __cxxabiv1
   int
   __cxa_atexit(void (*)(void*), void*, void*) _GLIBCXX_NOTHROW;
 
-  int
+  void
   __cxa_finalize(void*);
 
   // TLS destruction.


                 reply	other threads:[~2020-05-19  9:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200519090856.93F6F397A4AE@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).