All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	mingo@kernel.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/3] compiler.h: enable builtin overflow checkers and add fallback code
Date: Sun, 19 Jul 2015 23:47:18 -0400	[thread overview]
Message-ID: <55AC6F46.80606@oracle.com> (raw)
In-Reply-To: <1437347852-24921-1-git-send-email-linux@rasmusvillemoes.dk>

On 07/19/2015 07:17 PM, Rasmus Villemoes wrote:
> Last year, Sasha Levin suggested adding wrappers for the
> __builtin_*_overflow functions introduced with gcc 5.1 (based on
> similar, but type-specific, functions in clang). This is another
> attempt at providing such wrappers and fallback code for older compilers.

What's the difference between this version and the one Linus essentially
rejected?

I still think it's a good idea, but I'm not sure if anything changed since
last year.


Thanks,
Sasha

  parent reply	other threads:[~2015-07-20  3:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 23:17 [RFC 1/3] compiler.h: enable builtin overflow checkers and add fallback code Rasmus Villemoes
2015-07-19 23:17 ` [RFC 2/3] lib: add runtime test of check_*_overflow functions Rasmus Villemoes
2015-07-19 23:17 ` [RFC 3/3] slab.h: use check_mul_overflow in kmalloc_array Rasmus Villemoes
2015-07-19 23:17   ` Rasmus Villemoes
2015-07-20  3:47 ` Sasha Levin [this message]
2015-07-20 20:13   ` [RFC 1/3] compiler.h: enable builtin overflow checkers and add fallback code Rasmus Villemoes
2015-07-21  7:26     ` Ingo Molnar

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=55AC6F46.80606@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mingo@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.