public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] Cygwin: Make native clipboard layout same for 32- and 64-bit
Date: Sat, 9 Oct 2021 15:29:33 +0100	[thread overview]
Message-ID: <7dd31f61-43a1-4e4d-2e1a-dc79606263d5@dronecode.org.uk> (raw)
In-Reply-To: <29514de9-0d19-0d22-b8e1-3bfbce11589b@cornell.edu>

On 07/10/2021 06:22, Mark Geisert wrote:
 > The cygutils package has two programs, putclip and getclip, that also
 > depend on the layout of the cygcb_t.  At present they have duplicate
 > defs of struct cygcb_t defined here as no Cygwin header provides it.

This struct should maybe be in sys/cygwin.h or similar, if it's expected 
to be used in user-space as well.

On 09/10/2021 15:19, Ken Brown wrote:
> On 10/8/2021 5:52 AM, Takashi Yano wrote:
>> How about simply just:
>>
>> diff --git a/winsup/cygwin/fhandler_clipboard.cc 
>> b/winsup/cygwin/fhandler_clipboard.cc
>> index ccdb295f3..d822f4fc4 100644
>> --- a/winsup/cygwin/fhandler_clipboard.cc
>> +++ b/winsup/cygwin/fhandler_clipboard.cc
>> @@ -28,9 +28,10 @@ static const WCHAR *CYGWIN_NATIVE = 
>> L"CYGWIN_NATIVE_CLIPBOARD";
>>   typedef struct
>>   {
>> -  timestruc_t    timestamp;
>> -  size_t    len;
>> -  char        data[1];
>> +  uint64_t tv_sec;
>> +  uint64_t tv_nsec;
>> +  uint64_t len;
>> +  char data[1];
>>   } cygcb_t;
> 
> The only problem with this is that it might leave readers scratching 
> their heads unless they look at the commit that introduced this.  What 

I think the solution to that is a "comment" like "we don't use 'struct 
timespec' here as it's different size on different arches and that 
causes problem XYZ".

(I think that's preferable to conditional code which we assert (but 
don't ensure) is the same on all arches)

  reply	other threads:[~2021-10-09 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07  5:22 Mark Geisert
2021-10-07  5:56 ` Mark Geisert
2021-10-08  9:52 ` Takashi Yano
2021-10-09 14:19   ` Ken Brown
2021-10-09 14:29     ` Jon Turney [this message]
2021-10-09 14:43       ` Ken Brown
2021-10-11  6:13         ` Mark Geisert
2021-10-11 12:11           ` Ken Brown
2021-10-22 15:11             ` Corinna Vinschen
2021-10-23  5:35               ` Mark Geisert
2021-10-23 20:32                 ` Ken Brown
2021-10-23 21:53                   ` Mark Geisert
2021-10-23 23:58               ` Takashi Yano
2021-10-25  8:28                 ` Corinna Vinschen

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=7dd31f61-43a1-4e4d-2e1a-dc79606263d5@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).