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/112989] [14 Regression] GC ICE with C++, `#include <arm_sve.h>` and `-fsanitize=address` Date: Fri, 12 Jan 2024 12:29:40 +0000 [thread overview] Message-ID: <bug-112989-4-huH5pYqif3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112989-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112989 --- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:81d309168b2a058d4c8ad5430abb56cfe1f82188 commit r14-7185-g81d309168b2a058d4c8ad5430abb56cfe1f82188 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Fri Jan 12 12:29:22 2024 +0000 aarch64: Use a global map to detect duplicated overloads [PR112989] As explained in the covering note to the previous patch, the fact that aarch64-sve-* is now used for multiple header files means that function_builder::add_overloaded_function now needs to use a global map to detect duplicated overload functions, instead of the member variable that it used previously. gcc/ PR target/112989 * config/aarch64/aarch64-sve-builtins.h (function_builder::m_overload_names): Replace with... * config/aarch64/aarch64-sve-builtins.cc (overload_names): ...this new global. (add_overloaded_function): Update accordingly, using get_identifier to get a GGC-friendly record of the name.
next prev parent reply other threads:[~2024-01-12 12:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 20:09 [Bug target/112989] New: " pinskia at gcc dot gnu.org 2023-12-12 21:07 ` [Bug target/112989] " mpolacek at gcc dot gnu.org 2023-12-12 21:34 ` pinskia at gcc dot gnu.org 2023-12-12 21:58 ` pinskia at gcc dot gnu.org 2023-12-12 22:15 ` pinskia at gcc dot gnu.org 2023-12-12 22:40 ` pinskia at gcc dot gnu.org 2024-01-09 18:53 ` [Bug target/112989] [14 Regression] " pinskia at gcc dot gnu.org 2024-01-09 20:07 ` pinskia at gcc dot gnu.org 2024-01-09 20:52 ` pinskia at gcc dot gnu.org 2024-01-10 13:28 ` rguenth at gcc dot gnu.org 2024-01-10 14:21 ` jakub at gcc dot gnu.org 2024-01-10 14:43 ` rsandifo at gcc dot gnu.org 2024-01-10 14:46 ` jakub at gcc dot gnu.org 2024-01-10 14:50 ` rsandifo at gcc dot gnu.org 2024-01-12 12:29 ` cvs-commit at gcc dot gnu.org 2024-01-12 12:29 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-12 12:36 ` rsandifo at gcc dot gnu.org 2024-01-23 11:11 ` cvs-commit 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-112989-4-huH5pYqif3@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).