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 target/95154] [11 regression] FAIL: g++.dg/abi/pure-virtual1.C -std=c++14 (test for excess errors) Date: Thu, 04 Jun 2020 08:04:08 +0000 [thread overview] Message-ID: <bug-95154-4-i29LEnxHH5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95154-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95154 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andreas Schwab <schwab@gcc.gnu.org>: https://gcc.gnu.org/g:9b4e77e807e0099c3cfbf9c5b0c9e4154b9cb7a0 commit r11-896-g9b4e77e807e0099c3cfbf9c5b0c9e4154b9cb7a0 Author: Andreas Schwab <schwab@suse.de> Date: Fri May 15 17:38:30 2020 +0200 Fix missing assemble_external in ASM_OUTPUT_FDESC When TARGET_VTABLE_USES_DESCRIPTORS is defined then function pointers in the vtable are output by ASM_OUTPUT_FDESC. The only current user of this is ia64, but its implementation of ASM_OUTPUT_FDESC lacks a call to assemble_external. Thus if there is no other reference to the function the weak declaration for it will be missing. PR target/95154 * config/ia64/ia64.h (ASM_OUTPUT_FDESC): Call assemble_external.
next prev parent reply other threads:[~2020-06-04 8:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-15 14:38 [Bug target/95154] New: " schwab@linux-m68k.org 2020-05-15 15:35 ` [Bug target/95154] " schwab@linux-m68k.org 2020-05-18 5:54 ` rguenth at gcc dot gnu.org 2020-06-04 8:04 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-09 13:18 ` schwab@linux-m68k.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-95154-4-i29LEnxHH5@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).