On Wed, Oct 10, 2018 at 7:48 PM, Masahiro Yamada
wrote:
> On Wed, Oct 10, 2018 at 11:51 PM Kees Cook wrote:
>>
>> On Wed, Oct 10, 2018 at 12:03 AM, Miguel Ojeda
>> wrote:
>> > On Wed, Oct 10, 2018 at 8:12 AM Joel Stanley wrote:
>> >>
>> >> On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
>> >> >
On Wed, Oct 10, 2018 at 11:51 PM Kees Cook wrote:
>
> On Wed, Oct 10, 2018 at 12:03 AM, Miguel Ojeda
> wrote:
> > On Wed, Oct 10, 2018 at 8:12 AM Joel Stanley wrote:
> >>
> >> On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
> >> >
> >> > Yeah, that's what I'd linked to in the patchwork URL. Andr
On Wed, Oct 10, 2018 at 12:03 AM, Miguel Ojeda
wrote:
> On Wed, Oct 10, 2018 at 8:12 AM Joel Stanley wrote:
>>
>> On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
>> >
>> > Yeah, that's what I'd linked to in the patchwork URL. Andrew, can you take
>> > this?
>>
>> clang built -next is blowing up
On Wed, Oct 10, 2018 at 8:12 AM Joel Stanley wrote:
>
> On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
> >
> > Yeah, that's what I'd linked to in the patchwork URL. Andrew, can you take
> > this?
>
> clang built -next is blowing up now that Kees' -Wvla patch has been
> included. This patch fixes
On Thu, 27 Sep 2018 at 05:07, Kees Cook wrote:
>
> On Wed, Sep 26, 2018 at 12:29 PM, Nick Desaulniers
> wrote:
> > On Wed, Sep 26, 2018 at 12:03 PM Greg KH wrote:
> >>
> >> On Wed, Sep 26, 2018 at 11:45:19AM -0700, Kees Cook wrote:
> >> > On Wed, Sep 26, 2018 at 11:42 AM, Greg KH
> >> > wrote:
On Wed, Sep 26, 2018 at 12:29 PM, Nick Desaulniers
wrote:
> On Wed, Sep 26, 2018 at 12:03 PM Greg KH wrote:
>>
>> On Wed, Sep 26, 2018 at 11:45:19AM -0700, Kees Cook wrote:
>> > On Wed, Sep 26, 2018 at 11:42 AM, Greg KH
>> > wrote:
>> > > I'm not digging up a compiler.h patch from a web site an
On Wed, Sep 26, 2018 at 12:03 PM Greg KH wrote:
>
> On Wed, Sep 26, 2018 at 11:45:19AM -0700, Kees Cook wrote:
> > On Wed, Sep 26, 2018 at 11:42 AM, Greg KH
> > wrote:
> > > I'm not digging up a compiler.h patch from a web site and adding it to
> > > the tree this late in the release cycle. Esp
On Wed, Sep 26, 2018 at 11:45:19AM -0700, Kees Cook wrote:
> On Wed, Sep 26, 2018 at 11:42 AM, Greg KH wrote:
> > I'm not digging up a compiler.h patch from a web site and adding it to
> > the tree this late in the release cycle. Especially given that it
> > hasn't had any testing anywhere...
>
On Wed, Sep 26, 2018 at 11:42 AM, Greg KH wrote:
> I'm not digging up a compiler.h patch from a web site and adding it to
> the tree this late in the release cycle. Especially given that it
> hasn't had any testing anywhere...
Good point about it not living in -next.
Who should be carrying thes
On Wed, Sep 26, 2018 at 11:26:46AM -0700, Kees Cook wrote:
> On Wed, Sep 26, 2018 at 11:03 AM, Nick Desaulniers
> wrote:
> > On Wed, Sep 26, 2018 at 11:00 AM Matthias Kaehlcke
> > wrote:
> >>
> >> On Fri, Aug 31, 2018 at 09:46:02AM -0700, Nick Desaulniers wrote:
> >> > On Tue, Aug 28, 2018 at 4:
On Wed, Sep 26, 2018 at 11:03 AM, Nick Desaulniers
wrote:
> On Wed, Sep 26, 2018 at 11:00 AM Matthias Kaehlcke wrote:
>>
>> On Fri, Aug 31, 2018 at 09:46:02AM -0700, Nick Desaulniers wrote:
>> > On Tue, Aug 28, 2018 at 4:00 PM Nick Desaulniers
>> > wrote:
>> > >
>> > > On Mon, Aug 27, 2018 at 1:
On Wed, Sep 26, 2018 at 11:00 AM Matthias Kaehlcke wrote:
>
> On Fri, Aug 31, 2018 at 09:46:02AM -0700, Nick Desaulniers wrote:
> > On Tue, Aug 28, 2018 at 4:00 PM Nick Desaulniers
> > wrote:
> > >
> > > On Mon, Aug 27, 2018 at 1:42 PM Daniel Santos
> > > wrote:
> > > >
> > > > Hello Nick,
> >
On Fri, Aug 31, 2018 at 09:46:02AM -0700, Nick Desaulniers wrote:
> On Tue, Aug 28, 2018 at 4:00 PM Nick Desaulniers
> wrote:
> >
> > On Mon, Aug 27, 2018 at 1:42 PM Daniel Santos
> > wrote:
> > >
> > > Hello Nick,
> > >
> > > On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
> > > >>> Let's give
On Tue, Aug 28, 2018 at 4:00 PM Nick Desaulniers
wrote:
>
> On Mon, Aug 27, 2018 at 1:42 PM Daniel Santos wrote:
> >
> > Hello Nick,
> >
> > On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
> > >>> Let's give up __compiletime_assert_fallback(). This commit does not
> > >>> change the current beha
On Mon, Aug 27, 2018 at 1:42 PM Daniel Santos wrote:
>
> Hello Nick,
>
> On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
> >>> Let's give up __compiletime_assert_fallback(). This commit does not
> >>> change the current behavior since it just rips off the useless code.
> >> Clang is not the only
2018-08-28 19:55 GMT+09:00 Arnd Bergmann :
> On Mon, Aug 27, 2018 at 10:44 PM Daniel Santos
> wrote:
>>
>> On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
>> >> Now we're back to the question of "what do you mean by 'constant'"? If
>> >> you mean a C constant expression (as defined in the C stan
On Mon, Aug 27, 2018 at 10:44 PM Daniel Santos wrote:
>
> On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
> >> Now we're back to the question of "what do you mean by 'constant'"? If
> >> you mean a C constant expression (as defined in the C standard) than
> >> almost none of this code fits that c
On Mon, Aug 27, 2018 at 1:42 PM Daniel Santos wrote:
>
> Hello Nick,
>
> On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
> >> Now we're back to the question of "what do you mean by 'constant'"? If
> >> you mean a C constant expression (as defined in the C standard) than
> >> almost none of this c
Hello Nick,
On 08/27/2018 03:09 PM, Nick Desaulniers wrote:
>> Now we're back to the question of "what do you mean by 'constant'"? If
>> you mean a C constant expression (as defined in the C standard) than
>> almost none of this code fits that criteria. For these compile-time
>> assertions to wo
On Mon, Aug 27, 2018 at 1:05 PM Daniel Santos wrote:
>
> Hello Masahiro,
>
>
> On 08/25/2018 01:16 PM, Masahiro Yamada wrote:
> > __compiletime_assert_fallback() is supposed to stop building earlier
> > by using the negative-array-size method in case the compiler does not
> > support "error" attri
Hello Masahiro,
On 08/25/2018 01:16 PM, Masahiro Yamada wrote:
> __compiletime_assert_fallback() is supposed to stop building earlier
> by using the negative-array-size method in case the compiler does not
> support "error" attribute, but has never worked like that.
>
> You can simply try:
>
>
21 matches
Mail list logo
