From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Brad Smith <brad@comstyle.com>
Cc: Thomas Huth <thuth@redhat.com>,
Juan Quintela <quintela@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] migration: Remove time_t cast for OpenBSD
Date: Thu, 1 Apr 2021 09:14:24 +0100 [thread overview]
Message-ID: <YGWA4MSRe9JUmGqC@redhat.com> (raw)
In-Reply-To: <31adf621-ab77-3ac3-5995-501ac87426b3@comstyle.com>
On Wed, Mar 31, 2021 at 03:26:16PM -0400, Brad Smith wrote:
> On 3/13/2021 6:33 PM, Brad Smith wrote:
> > On 3/11/2021 1:39 PM, Daniel P. Berrangé wrote:
> > > On Thu, Mar 11, 2021 at 06:28:57PM +0000, Dr. David Alan Gilbert wrote:
> > > > * Laurent Vivier (laurent@vivier.eu) wrote:
> > > > > Le 08/03/2021 à 12:46, Thomas Huth a écrit :
> > > > > > On 22/02/2021 08.28, Brad Smith wrote:
> > > > > > > OpenBSD has supported 64-bit time_t across all archs
> > > > > > > since 5.5 released in 2014.
> > > > > > >
> > > > > > > Remove a time_t cast that is no longer necessary.
> > > > > > >
> > > > > > >
> > > > > > > Signed-off-by: Brad Smith <brad@comstyle.com>
> > > > > > >
> > > > > > > diff --git a/migration/savevm.c b/migration/savevm.c
> > > > > > > index 52e2d72e4b..9557f85ba9 100644
> > > > > > > --- a/migration/savevm.c
> > > > > > > +++ b/migration/savevm.c
> > > > > > > @@ -2849,8 +2849,7 @@ bool save_snapshot(const char
> > > > > > > *name, bool overwrite, const char *vmstate,
> > > > > > > if (name) {
> > > > > > > pstrcpy(sn->name, sizeof(sn->name), name);
> > > > > > > } else {
> > > > > > > - /* cast below needed for OpenBSD where
> > > > > > > tv_sec is still 'long' */
> > > > > > > - localtime_r((const time_t *)&tv.tv_sec, &tm);
> > > > > > > + localtime_r(&tv.tv_sec, &tm);
> > > > > > > strftime(sn->name, sizeof(sn->name),
> > > > > > > "vm-%Y%m%d%H%M%S", &tm);
> > > > > > > }
> > > > > but the qemu_timeval from "include/sysemu/os-win32.h" still
> > > > > uses a long: is this file compiled for
> > > > > win32?
> > > > Yep this fails for me when built with x86_64-w64-mingw32- (it's fine
> > > > with i686-w64-mingw32- )
> > > We could just switch the code to use GDateTime from GLib and thus
> > > avoid portability issues. I think this should be equivalent:
> > >
> > > g_autoptr(GDateTime) now = g_date_time_new_now_local();
> > > g_autofree char *nowstr = g_date_time_format(now,
> > > "vm-%Y%m%d%H%M%s");
> > > strncpy(sn->name, sizeof(sn->name), nowstr);
> >
> > Which way do you guys want to go? Something like above, remove the
> > comment
> > or some variation on the comment but not mentioning OpenBSD since it is
> > no
> > longer relevant?
>
> Anyone?
Personally I always favour using GLib APIs if there's an applicable one,
since it eliminates portability problems - or rather offloads them to
the GLib maintainers, who have already solved them generally.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-04-01 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 7:28 [PATCH] migration: Remove time_t cast for OpenBSD Brad Smith
2021-03-08 11:46 ` Thomas Huth
2021-03-09 21:08 ` Laurent Vivier
2021-03-11 18:28 ` Dr. David Alan Gilbert
2021-03-11 18:39 ` Daniel P. Berrangé
2021-03-13 23:33 ` Brad Smith
2021-03-31 19:26 ` Brad Smith
2021-04-01 8:14 ` Daniel P. Berrangé [this message]
2021-04-01 17:14 ` Brad Smith
2021-03-09 21:38 ` Brad Smith
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=YGWA4MSRe9JUmGqC@redhat.com \
--to=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=dgilbert@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).