Fw: Re: [RE-SENDING]Re: MCSoC2013: to enhance embedded Linux for many-core system

2012-12-17 Thread ETANI NORIKO
-Forwarded message- From: ETANI NORIKO To: iant Date: Sun, 16 Dec 2012 21:34:48 +0900 (JST) Subject: Re: [RE-SENDING]Re: MCSoC2013: to enhance embedded Linux for many-core system Dear Sir, I would like to add my explanation to my former e-mail. >>The reason why GCC is not available f

Fw: [RE-SENDING]Re: MCSoC2013: to enhance embedded Linux for many-core system

2012-12-17 Thread ETANI NORIKO
-Forwarded message- From: ETANI NORIKO To: iant Date: Sun, 16 Dec 2012 21:26:34 +0900 (JST) Subject: [RE-SENDING]Re: MCSoC2013: to enhance embedded Linux for many-core system Dear Sir, Thank you for replying my e-mail. This is an implementation issue for OpenCL or parallel computing

Re: How does address sanitizer handle read-modify-write memory access?

2012-12-17 Thread Jakub Jelinek
On Mon, Dec 17, 2012 at 11:12:43AM +0100, Dodji Seketeli wrote: > Konstantin Serebryany a écrit: > > > When we have a code like X++ (either RMW, or a regular increment) it > > is enough for asan to instrument it just once (either as a read or a > > write, doesn't matter). > > LLVM implementation

Re: How does address sanitizer handle read-modify-write memory access?

2012-12-17 Thread Dodji Seketeli
Konstantin Serebryany a écrit: > When we have a code like X++ (either RMW, or a regular increment) it > is enough for asan to instrument it just once (either as a read or a > write, doesn't matter). > LLVM implementation does this optimization for regular increments, > while GCC does not (yet). >