public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/65480] libstdc++-prettyprinters/libfundts.cc test failures on powerpc64 Date: Wed, 02 Dec 2020 21:39:28 +0000 [thread overview] Message-ID: <bug-65480-4-jYHlT0Mxgs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65480-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65480 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:dc2b372ed1b1e9af6db45051cff95478c7616807 commit r11-5683-gdc2b372ed1b1e9af6db45051cff95478c7616807 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Dec 2 21:39:08 2020 +0000 libstdc++: Fix std::any pretty printer [PR 68735] This fixes errors seen on powerpc64 (big endian only) due to the printers for std::any and std::experimental::any being unable to find the manager function. libstdc++-v3/ChangeLog: PR libstdc++/65480 PR libstdc++/68735 * python/libstdcxx/v6/printers.py (function_pointer_to_name): New helper function to get the name of a function from its address. (StdExpAnyPrinter.__init__): Use it.
next prev parent reply other threads:[~2020-12-02 21:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-20 0:00 [Bug libstdc++/65480] New: libstdc++-prettyprinters/libfundts.cc test failures on powepc64 msebor at gcc dot gnu.org 2015-03-24 15:30 ` [Bug libstdc++/65480] " redi at gcc dot gnu.org 2015-03-24 15:35 ` redi at gcc dot gnu.org 2020-12-02 21:38 ` [Bug libstdc++/65480] libstdc++-prettyprinters/libfundts.cc test failures on powerpc64 redi at gcc dot gnu.org 2020-12-02 21:39 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-02 21:40 ` redi at gcc dot gnu.org 2021-01-11 15:04 ` cvs-commit at gcc dot gnu.org 2021-01-11 17:44 ` cvs-commit at gcc dot gnu.org 2021-01-11 17:46 ` redi at gcc dot gnu.org
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=bug-65480-4-jYHlT0Mxgs@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).