public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107453] New stdarg tests in r13-3549-g4fe34cdcc80ac2 fail Date: Mon, 31 Oct 2022 17:08:58 +0000 [thread overview] Message-ID: <bug-107453-4-07eKiZ4pKY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107453-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107453 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-10-31 Build|powerpc64-linux-gnu, | |powerpc64le-linux-gnu | Host|powerpc64-linux-gnu, | |powerpc64le-linux-gnu | CC| |ebotcazou at gcc dot gnu.org Target|powerpc64-linux-gnu, | |powerpc64le-linux-gnu | Status|UNCONFIRMED |NEW --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- Likewise on SPARC64. It's a TARGET_STRICT_ARGUMENT_NAMING target, so we have in expand_call: /* Count the arguments and set NUM_ACTUALS. */ num_actuals = call_expr_nargs (exp) + num_complex_actuals + structure_value_addr_parm; /* Compute number of named args. First, do a raw count of the args for INIT_CUMULATIVE_ARGS. */ if (type_arg_types != 0) n_named_args = (list_length (type_arg_types) /* Count the struct value address, if it is passed as a parm. */ + structure_value_addr_parm); else /* If we know nothing, treat all args as named. */ n_named_args = num_actuals; which yields n_named_args = num_actuals since type_arg_types == 0 and then: if (type_arg_types != 0 && targetm.calls.strict_argument_naming (args_so_far)) ; so n_named_args = num_actuals in the end and the game is over.
next prev parent reply other threads:[~2022-10-31 17:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-28 21:39 [Bug other/107453] New: " seurer at gcc dot gnu.org 2022-10-28 21:42 ` [Bug target/107453] " pinskia at gcc dot gnu.org 2022-10-31 17:08 ` ebotcazou at gcc dot gnu.org [this message] 2022-11-05 9:34 ` tschwinge at gcc dot gnu.org 2022-11-05 10:23 ` [Bug target/107453] [13 Regression] " rguenth at gcc dot gnu.org 2022-11-07 8:51 ` chenglulu at loongson dot cn 2023-01-06 14:00 ` jakub at gcc dot gnu.org 2023-01-09 12:37 ` cvs-commit at gcc dot gnu.org 2023-01-09 12:44 ` jakub at gcc dot gnu.org 2023-01-09 20:07 ` tschwinge at gcc dot gnu.org 2023-03-15 12:39 ` xry111 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-107453-4-07eKiZ4pKY@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).