public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105946] [12/13 Regression] ICE in maybe_warn_pass_by_reference, at tree-ssa-uninit.cc:843 Date: Tue, 14 Jun 2022 09:09:49 +0000 [thread overview] Message-ID: <bug-105946-4-2TQdZDosIU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105946 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-06-14 Priority|P3 |P2 Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Keywords| |needs-reduction Target Milestone|--- |12.2 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. (gdb) p debug_gimple_stmt (stmt) # .MEM_8 = VDEF <.MEM_7(D)> _2 = std::__new_allocator<std::vector<T> >::allocate (__n_1(D), 0B); 842 tree arg = gimple_call_arg (stmt, argno - 1); (gdb) p argno $2 = 3 (gdb) p debug_generic_expr (fntype) struct vector * __new_allocator::<T514c> (struct __new_allocator *, size_type, const void *) so the number of actual arguments does not match the function type of the call. I have a simple patch.
next prev parent reply other threads:[~2022-06-14 9:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 12:58 [Bug c++/105946] New: " gscfq@t-online.de 2022-06-14 9:09 ` rguenth at gcc dot gnu.org [this message] 2022-06-14 10:53 ` [Bug c++/105946] " cvs-commit at gcc dot gnu.org 2022-06-14 10:54 ` [Bug c++/105946] [12 " rguenth at gcc dot gnu.org 2022-07-15 11:21 ` marxin at gcc dot gnu.org 2022-07-19 11:37 ` cvs-commit at gcc dot gnu.org 2022-07-19 11:38 ` rguenth 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-105946-4-2TQdZDosIU@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).