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 c++/98626] UBSAN: vec.h:591:30: runtime error: member access within null pointer of type 'struct vec' Date: Wed, 13 Jan 2021 13:18:33 +0000 [thread overview] Message-ID: <bug-98626-4-NjwirVND9g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98626-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98626 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>: https://gcc.gnu.org/g:11cbea852b0ae2b0f17a9caeaf6344d689231c2f commit r11-6647-g11cbea852b0ae2b0f17a9caeaf6344d689231c2f Author: Nathan Sidwell <nathan@acm.org> Date: Wed Jan 13 05:13:12 2021 -0800 c++: Fix cp_build_function_call_vec [PR 98626] I misunderstood the cp_build_function_call_vec API, thinking a NULL vector was an acceptable way of passing no arguments. You need to pass a vector of no elements. PR c++/98626 gcc/cp/ * module.cc (module_add_import_initializers): Pass a zero-element argument vector.
next prev parent reply other threads:[~2021-01-13 13:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 17:01 [Bug c++/98626] New: " marxin at gcc dot gnu.org 2021-01-11 17:02 ` [Bug c++/98626] " marxin at gcc dot gnu.org 2021-01-13 12:35 ` nathan at gcc dot gnu.org 2021-01-13 13:18 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-13 13:35 ` nathan 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-98626-4-NjwirVND9g@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).