> On Jun 28, 2020, at 10:24 AM, Robert Elz wrote:
>
>Date:Sat, 27 Jun 2020 11:49:30 -0400
>From:"Christos Zoulas"
>Message-ID: <20200627154930.84e22f...@cvs.netbsd.org>
>
> | Modified Files:
> |src/sys/compat/sys: mount.h
> |
> | Log Message:
> | Ignore t
Date:Sat, 27 Jun 2020 11:49:30 -0400
From:"Christos Zoulas"
Message-ID: <20200627154930.84e22f...@cvs.netbsd.org>
| Modified Files:
| src/sys/compat/sys: mount.h
|
| Log Message:
| Ignore the supplied size, and always use the argument size that we know.
On Fri, Jun 28, 2019 at 05:03:37AM -0700, Jason Thorpe wrote:
>
> > On Jun 26, 2019, at 7:10 PM, matthew green wrote:
> >
> >> Always include the 32 bit structure and definitions on _LP64 regardless
> >> of compat32 being on or off, because we want the headers to work when
> >> compiling modular
> On Jun 26, 2019, at 7:10 PM, matthew green wrote:
>
>> Always include the 32 bit structure and definitions on _LP64 regardless
>> of compat32 being on or off, because we want the headers to work when
>> compiling modular kernels. Of course the 32 bit structs do not make sense
>> on platforms
> Always include the 32 bit structure and definitions on _LP64 regardless
> of compat32 being on or off, because we want the headers to work when
> compiling modular kernels. Of course the 32 bit structs do not make sense
> on platforms that don't have 32 bit modes (alpha), but we don't have
> a de
> Date: Fri, 15 Jun 2018 19:55:28 +0700
> From: Robert Elz
>
> Another way would be
>
> static const struct timespec50 zts = { 0 };
> and
> *ts50 = zts;
I have nothing substantive to add about the question at hand, but one
tiny nit: there is no need for the initializer in this case,
On Fri, Jun 15, 2018 at 17:11:49 +0300, Valery Ushakov wrote:
> It seems that with restrict we can just memset the whole struct and
> the compiler will elide the memset completely when there's no pad to
> scrub.
Alas, with the real code the compiler cannot elide the memset. :(
-uwe
On Fri, Jun 15, 2018 at 19:55:28 +0700, Robert Elz wrote:
> Date:Fri, 15 Jun 2018 12:41:56 +0300
> From:Valery Ushakov
> Message-ID: <20180615094156.gd3...@pony.stderr.spb.ru>
>
> | Re memset - I now wonder if
> | compiler is even allowed to be smart here b/c str
Date:Fri, 15 Jun 2018 12:41:56 +0300
From:Valery Ushakov
Message-ID: <20180615094156.gd3...@pony.stderr.spb.ru>
| Re memset - I now wonder if
| compiler is even allowed to be smart here b/c strict aliasing
Another way would be
static const struct timespe
On Fri, Jun 15, 2018 at 18:05:29 +1000, matthew green wrote:
> "Robert Elz" writes:
> > Module Name:src
> > Committed By: kre
> > Date: Fri Jun 15 07:46:59 UTC 2018
> >
> > Modified Files:
> > src/sys/compat/sys: time_types.h
> >
> > Log Message:
> > If we are goi
"Robert Elz" writes:
> Module Name: src
> Committed By: kre
> Date: Fri Jun 15 07:46:59 UTC 2018
>
> Modified Files:
> src/sys/compat/sys: time_types.h
>
> Log Message:
> If we are going to use offsetof() we'd need to include to
> get it defined. Rather than deal with potential n
On Tue, 20 Dec 2011, Alan Barrett wrote:
On Tue, 20 Dec 2011, Matthias Drochner wrote:
Modified Files:
src/sys/compat/sys: rnd.h
Log Message:
allow kernels w/o COMPAT_50 to build
What was the actual problem? Nothing defined by this file is
supposed to be used in a kernel without COMP
On Tue, 20 Dec 2011, Matthias Drochner wrote:
Module Name:src
Committed By: drochner
Date: Tue Dec 20 16:38:06 UTC 2011
Modified Files:
src/sys/compat/sys: rnd.h
Log Message:
allow kernels w/o COMPAT_50 to build
What was the actual problem? Nothing defined by this fil
13 matches
Mail list logo