Re: making the new if-converter not mangle IR that is already vectorizer-friendly

2015-07-02 Thread Abe
On 7/2/15 4:30 AM, Alan Lawrence wrote: Hi, pleased to meet you :) Likewise. :-) [Abe wrote:] * Always safe for stores, sometimes a little risky for loads: speculative loads might cause multithreaded programs with insufficient locking to fail due to writes by another thread being

Re: libgomp: Purpose of gomp_thread_pool::last_team?

2015-07-02 Thread Jakub Jelinek
On Thu, Jul 02, 2015 at 09:57:20PM +0200, Sebastian Huber wrote: > does anyone know what the purpose of gomp_thread_pool::last_team is? This > field seems to be used to delay the team destruction in gomp_team_end() in > case the team has more than one thread and the previous team state has no >

libgomp: Purpose of gomp_thread_pool::last_team?

2015-07-02 Thread Sebastian Huber
Hello, does anyone know what the purpose of gomp_thread_pool::last_team is? This field seems to be used to delay the team destruction in gomp_team_end() in case the team has more than one thread and the previous team state has no team associated (identifies this a master thread?): if (__buil

Re: GCC 5.1.1 Status Report (2015-06-22)

2015-07-02 Thread Matthew Wahab
On 02/07/15 13:40, Ramana Radhakrishnan wrote: On Thu, Jul 2, 2015 at 12:03 PM, Matthew Wahab wrote: I'd like to get the fix for PR target/65697 (weak memory barriers for __sync builtins on ARMv8) into GCC-5.2. I'd also like to see the ARM patches backported please unless there are RM objec

%fs and %gs segments on x86/x86-64

2015-07-02 Thread Armin Rigo
Hi all, I implemented support for %fs and %gs segment prefixes on the x86 and x86-64 platforms, in what turns out to be a small patch. For those not familiar with it, at least on x86-64, %fs and %gs are two special registers that a user program can ask be added to any address machine instruction.

Re: Consideration of Cost associated with SEME regions.

2015-07-02 Thread Vladimir Makarov
On 07/02/2015 07:06 AM, Ajit Kumar Agarwal wrote: Sorry for the typo error. I meant exits instead of exists. The below is corrected. The Cost Calculation for a candidate to Spill in the Integrated Register Allocator(IRA) considers only the SESE regions. The Cost Calculation in the IRA should

Re: GCC 5.1.1 Status Report (2015-06-22)

2015-07-02 Thread Ramana Radhakrishnan
On Thu, Jul 2, 2015 at 12:03 PM, Matthew Wahab wrote: > On 22/06/15 12:56, Richard Biener wrote: >> >> >> I plan to release GCC 5.2.0 around July 10th which means a release >> candidate being done around July 3rd. >> >> Please check your open regression bugs for ones that eligible for >> backporti

Re: GCC 5.1.1 Status Report (2015-06-22)

2015-07-02 Thread Richard Biener
On Thu, 2 Jul 2015, Matthew Wahab wrote: > On 22/06/15 12:56, Richard Biener wrote: > > > > I plan to release GCC 5.2.0 around July 10th which means a release > > candidate being done around July 3rd. > > > > Please check your open regression bugs for ones that eligible for > > backporting. Als

RE: Consideration of Cost associated with SEME regions.

2015-07-02 Thread Ajit Kumar Agarwal
Sorry for the typo error. I meant exits instead of exists. The below is corrected. The Cost Calculation for a candidate to Spill in the Integrated Register Allocator(IRA) considers only the SESE regions. The Cost Calculation in the IRA should consider the SEME regions into consideration for spi

Re: GCC 5.1.1 Status Report (2015-06-22)

2015-07-02 Thread Matthew Wahab
On 22/06/15 12:56, Richard Biener wrote: I plan to release GCC 5.2.0 around July 10th which means a release candidate being done around July 3rd. Please check your open regression bugs for ones that eligible for backporting. Also please help getting the P1 bug count to zero (there is still the

Consideration of Cost associated with SEME regions.

2015-07-02 Thread Ajit Kumar Agarwal
All: The Cost Calculation for a candidate to Spill in the Integrated Register Allocator(IRA) considers only the SESE regions. The Cost Calculation in the IRA should consider the SEME regions into consider for spilling decisions. The Cost associated with the path that has un-matured exists shou

Re: making the new if-converter not mangle IR that is already vectorizer-friendly

2015-07-02 Thread Alan Lawrence
Abe wrote: Hi, pleased to meet you :) As some of you already know, at SARC we are working on a new "if converter" to help convert simple "if"-based blocks of code that appear inside loops into an autovectorizer-friendly form that closely resembles the C ternary operator ["c ? x : y"]. G

Transformation from SEME(Single Entry Multiple Exit) to SESE(Single Entry Single Exit)

2015-07-02 Thread Ajit Kumar Agarwal
All: Single Entry and Multiple Exits disables traditional Loop optimization. The presence of short circuit also makes the CFG as Single Entry and Multiple Exits. The transformation from SEME(Single Entry and Multiple Exits) to SESE( Single Entry and Single Exits enables many Loop Optimizations.

configure --program-suffix could change gccjit library path?

2015-07-02 Thread Basile Starynkevitch
Hello All, Imagine that someone (e.g. a distribution packager) wants to have several versions of gccjit like he does have several versions of gcc. Concretely, GCC 5.2 with GCC 6.1 I would believe that the --program-suffix argument of /configure would be useful. So he/she would compile GCC 5