Re: Improving Asan code on ARM targets

+ eugeni.stepanov On Tue, Apr 29, 2014 at 10:04 AM, Andrew Pinski wrote: > On Mon, Apr 28, 2014 at 10:50 PM, Yury Gribov wrote: >> Hi all, >> >> I've recently noticed that GCC generates suboptimal code for Asan on ARM >> targets. E.g. for a 4-byte memory access check >> >> (shadow_val != 0)

Re: How to access points-to information for function pointers

On Monday 28 April 2014 02:46 PM, Richard Biener wrote: On Sat, Apr 26, 2014 at 4:07 PM, Richard Biener wrote: On April 26, 2014 12:31:34 PM CEST, Swati Rathi wrote: On Friday 25 April 2014 11:11 PM, Richard Biener wrote: On April 25, 2014 5:54:09 PM CEST, Swati Rathi wrote: Hello, I am

Re: Improving Asan code on ARM targets

On Mon, Apr 28, 2014 at 10:50 PM, Yury Gribov wrote: > Hi all, > > I've recently noticed that GCC generates suboptimal code for Asan on ARM > targets. E.g. for a 4-byte memory access check > > (shadow_val != 0) & (last_byte >= shadow_val) > > we get the following sequence: > > movr2, r

Improving Asan code on ARM targets

Hi all, I've recently noticed that GCC generates suboptimal code for Asan on ARM targets. E.g. for a 4-byte memory access check (shadow_val != 0) & (last_byte >= shadow_val) we get the following sequence: movr2, r0, lsr #3 andr3, r0, #7 addr3, r3, #3 addr2

Re: Add stdatomic.h

On Sun, 20 Apr 2014, Sebastian Huber wrote: > Hello, > > I test currently the GCC 4.9 release branch. Should work with > C++? I use GCC as a cross-compiler for RTEMS targets. RTEMS uses Newlib as C is very C-specific; C++ programs are expected to use instead (although it may be possible f

Re: OpenMP: Lowering to builtin function calls in the front ends, instead of creating trivial tree nodes?

On Mon, Apr 28, 2014 at 07:47:13PM +0200, Thomas Schwinge wrote: > While working on some OpenACC constructs in the C front end (notably > those tagged as »Executable Directives«, OpenACC 2.0, 2.12), Jim has > noticed that for a certain class of OpenMP constructs (corresponding in > "style" to the O

OpenMP: Lowering to builtin function calls in the front ends, instead of creating trivial tree nodes?

Hi! While working on some OpenACC constructs in the C front end (notably those tagged as »Executable Directives«, OpenACC 2.0, 2.12), Jim has noticed that for a certain class of OpenMP constructs (corresponding in "style" to the OpenACC Executable Directives), these are directly lowered to builtin

status of wide-int patch.

At this point we have believe that we have addressed all of the concerns that the community has made about the wide-int branch. We have also had each of the sections of the branch approved by the area maintainers. We are awaiting a clean build on the arm and are currently retesting x86-64, s

Re: c++ compiler results

#include #include #include #include #include // goal: make this code work with constexpr, tested on g++ 4.7.2 (-std=c++11) //#define constexpr std::string operator"" _s(const char *literal_string, size_t chars) { return std::string(literal_string, chars); } template constexpr bool ty

Re: Support to OpenACC and OpenMP 4.0 in GCC 4.9

Hi Paolo! On Mon, 28 Apr 2014 10:31:15 +0200, Paolo Leoni wrote: > I'm primarily a user of OpenACC. Be aware that there is not yet any actual offloading implemented on the gomp-4_0-branch. > Sorry, I'm a little newbie about GCC building, could you post here a > simple list of commands in order

Announcement of Wide-Int Reviewers

I am pleased to announce that the GCC Steering Committee has appointed Richard Sandiford, Mike Stump and Ken Zadeck as Wide-Int Reviewers. Please join me in congratulating Richard, Mike and Ken on their new role. Please update your listings in the MAINTAINERS file. Happy hacking!

Re: How to access points-to information for function pointers

On Sat, Apr 26, 2014 at 4:07 PM, Richard Biener wrote: > On April 26, 2014 12:31:34 PM CEST, Swati Rathi > wrote: >> >>On Friday 25 April 2014 11:11 PM, Richard Biener wrote: >>> On April 25, 2014 5:54:09 PM CEST, Swati Rathi >> wrote: Hello, I am trying to print points-to informa

Re: Support to OpenACC and OpenMP 4.0 in GCC 4.9

Hi Thomas, thank you for your response. I'm primarily a user of OpenACC. Sorry, I'm a little newbie about GCC building, could you post here a simple list of commands in order to building GCC 4.9 with openacc support? I've found this: http://gcc.1065356.n5.nabble.com/OpenACC-or-OpenMP-4-0-target-d

Re: SPARC LEON3 and CAS instruction

> Ok, this makes sense. Which default to you have in mind for the -muser-mode > option? -mno-user-mode the default, it's usually what's done in this case I think. -- Eric Botcazou

Re: SPARC LEON3 and CAS instruction

On 2014-04-28 10:02, Eric Botcazou wrote: Thanks, since this -muser-mode seems to be something new, maybe we should >instead use -mcas=supervisor|user to make it more specific? I don't think so, we might need to extend its purview in the future. Ok, this makes sense. Which default to you have

Re: SPARC LEON3 and CAS instruction

> Thanks, since this -muser-mode seems to be something new, maybe we should > instead use -mcas=supervisor|user to make it more specific? I don't think so, we might need to extend its purview in the future. -- Eric Botcazou

Re: SPARC LEON3 and CAS instruction

On 2014-04-25 18:31, Eric Botcazou wrote: recent GCC versions support the C11 atomic operations for the SPARC LEON3 processor via the CASA instruction. GCC emits CASA instructions with an ASI of 0x80. I think this is due to the usage of "cas" if I get the stuff in sync.md right: "(define_insn