public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/111716] call site parameter not matching with formal parameter Date: Fri, 06 Oct 2023 16:50:15 +0000 [thread overview] Message-ID: <bug-111716-4-fYRcjGsWkz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111716-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111716 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|riscv64-linux-gnu |riscv64-linux-gnu | |x86_64-linux-gnu | |aarch64-linux-gnu --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So it looks like the first argument is passed through with no change and that is not recorded ... It happens on x86_64, aarch64 too. The testcase I was using was the preprocessed source from bug 111680 and add to the following to the end: ``` void run_benchmark( void *vargs ) { struct bench_args_t *args = (struct bench_args_t *)vargs; bfs(args->nodes, args->edges, args->starting_node, args->level, args->level_counts); } ```
next prev parent reply other threads:[~2023-10-06 16:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-06 16:26 [Bug debug/111716] New: " king.chung at manchester dot ac.uk 2023-10-06 16:34 ` [Bug debug/111716] " pinskia at gcc dot gnu.org 2023-10-06 16:50 ` pinskia at gcc dot gnu.org [this message] 2023-10-06 16:52 ` king.chung at manchester dot ac.uk 2023-10-06 16:53 ` pinskia 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-111716-4-fYRcjGsWkz@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).