From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [pushed] Fix sim build failure
Date: Thu, 22 Apr 2021 21:56:40 -0400 [thread overview]
Message-ID: <46e3682d-e0e0-f6c3-07a7-a11e5b89e8d5@polymtl.ca> (raw)
In-Reply-To: <20210423015107.3841223-1-tom@tromey.com>
On 2021-04-22 9:51 p.m., Tom Tromey wrote:
> On x86-64 Fedora 32, the sim was failing to build.
> sim_events_schedule was passing a 'dummy' argument to
> sim_events_schedule_vtracef, which caused an error because the format
> parameter was NULL. However, removing this dummy argument caused an
> error because too few arguments were being passed -- catch 22.
>
> This patch fixes the build problem by using sim_events_schedule_tracef
> instead.
>
> sim/common/ChangeLog
> 2021-04-22 Tom Tromey <tom@tromey.com>
>
> * sim-events.c (sim_events_schedule): Use
> sim_events_schedule_tracef.
> ---
> sim/common/ChangeLog | 5 +++++
> sim/common/sim-events.c | 5 +----
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/sim/common/sim-events.c b/sim/common/sim-events.c
> index 207c8674d16..60e4c55a874 100644
> --- a/sim/common/sim-events.c
> +++ b/sim/common/sim-events.c
> @@ -469,10 +469,7 @@ sim_events_schedule (SIM_DESC sd,
> sim_event_handler *handler,
> void *data)
> {
> - va_list dummy;
> - memset (&dummy, 0, sizeof dummy);
> - return sim_events_schedule_vtracef (sd, delta_time, handler, data,
> - NULL, dummy);
> + return sim_events_schedule_tracef (sd, delta_time, handler, data, NULL);
> }
> #endif
>
>
Ah, good catch. Clang doesn't give this warning, and I didn't think of
building my patch with gcc, so I missed it. Using the tracef variant
looks better anyway.
Simon
next prev parent reply other threads:[~2021-04-23 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 1:51 Tom Tromey
2021-04-23 1:56 ` Simon Marchi via Gdb-patches [this message]
2021-04-23 2:16 ` Mike Frysinger via Gdb-patches
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=46e3682d-e0e0-f6c3-07a7-a11e5b89e8d5@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.com \
/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