Displaying 3 results from an estimated 3 matches for "f99504c8".
2012 Sep 20
0
[LLVMdev] Handling of unsafe functions
On Thu, Sep 20, 2012 at 10:13 AM, Chris Lattner <clattner at apple.com> wrote:
>
> On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote:
>
> > On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E
> > <javier.e.martinez at intel.com> wrote:
> >> We have identified functions in LLVM sources using a static code
> analyzer
>
2012 Sep 20
3
[LLVMdev] Handling of unsafe functions
On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote:
> On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E
> <javier.e.martinez at intel.com> wrote:
>> We have identified functions in LLVM sources using a static code analyzer
>> which are marked as a “security vulnerability”[1][2]. There has been work
>> already done to address some of
2012 Sep 21
5
[LLVMdev] Handling of unsafe functions
...we should change it to take an llvm::SmallVectorImpl<char>, rather than relying on a character buffer "which must be of sufficient size".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120921/f99504c8/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CStringFunctionsUse.txt
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120921/f99504c8/attachment.txt>