From: "cohenarthur at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/108631] gcc/rust/backend/rust-constexpr.cc:2099:33: error: too few arguments to function ‘tree_node* Rust::Compile::unshare_constructor(tree, const char*, int, const char*)’ with --enable-gather-detailed-mem-stats
Date: Wed, 22 Feb 2023 13:22:35 +0000 [thread overview]
Message-ID: <bug-108631-35322-6e3IPJEG4l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108631-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108631
Arthur Cohen <cohenarthur at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |cohenarthur at gcc dot gnu.org
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-02-22 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:07 [Bug rust/108631] New: " marxin at gcc dot gnu.org
2023-02-01 13:07 ` [Bug rust/108631] " marxin at gcc dot gnu.org
2023-02-09 14:55 ` cohenarthur at gcc dot gnu.org
2023-02-09 15:17 ` marxin at gcc dot gnu.org
2023-02-22 13:22 ` cohenarthur at gcc dot gnu.org [this message]
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-108631-35322-6e3IPJEG4l@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@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).