Re: ARM peephole2 from 2003 never merged, still valid

2019-06-05 Thread Segher Boessenkool
On Wed, Jun 05, 2019 at 05:02:53PM -0600, Jeff Law wrote: > On 6/2/19 6:28 AM, Segher Boessenkool wrote: > > On Sat, Jun 01, 2019 at 11:41:30PM +, Fredrik Hederstierna wrote: > >> +(define_peephole2 > >> + [(set (match_operand:SI 0 "arm_general_register_operand" "") > >> + (match_operand

Re: ARM peephole2 from 2003 never merged, still valid

2019-06-05 Thread Jeff Law
On 6/2/19 6:28 AM, Segher Boessenkool wrote: > On Sat, Jun 01, 2019 at 11:41:30PM +, Fredrik Hederstierna wrote: >> +(define_peephole2 >> + [(set (match_operand:SI 0 "arm_general_register_operand" "") >> + (match_operand:SI 1 "arm_general_register_operand" "")) >> + (set (reg:CC CC_REG

Re: Preventing ISO C errors when using macros for builtin types

2019-06-05 Thread Segher Boessenkool
On Wed, Jun 05, 2019 at 08:49:39PM +0100, Jozef Lawrynowicz wrote: > On Wed, 5 Jun 2019 11:49:21 -0500 > Segher Boessenkool wrote: > > The documentation says > > > > '-pedantic' and other options cause warnings for many GNU C extensions. > > You can prevent such warnings within one expression

On-Demand range technology [6/5] - Integration

2019-06-05 Thread Andrew MacLeod
After the various discussions, I've evaluated how I think everything can fit together, so this is my proposal for integration with trunk. The complete Ranger prototype consists of 5 major  components, one of which is missing/un-implemented as yet :-) 1 - irange -  This is the non-symboli

Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime

2019-06-05 Thread Janne Blomqvist
On Wed, Jun 5, 2019 at 10:42 PM 김규래 wrote: > > On Wed, Jun 5, 2019 at 9:25 PM 김규래 wrote: > > > > > > Hi, thanks for the detailed explanation. > > > I think I now get the picture. > > > Judging from my current understanding, the task-parallelism currently > works as follows: > > > 1. Tasks are pl

Re: Preventing ISO C errors when using macros for builtin types

2019-06-05 Thread Jozef Lawrynowicz
On Wed, 5 Jun 2019 11:49:21 -0500 Segher Boessenkool wrote: > On Wed, Jun 05, 2019 at 02:25:59PM +0100, Jozef Lawrynowicz wrote: > > I'm assuming it would not be valid to modify the behaviour of __extension__ > > so it can be placed within a declaration, and not just at the > > beginning. However

Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime

2019-06-05 Thread 김규래
> On Wed, Jun 5, 2019 at 9:25 PM 김규래 wrote: > > > Hi, thanks for the detailed explanation. > > I think I now get the picture. > > Judging from my current understanding, the task-parallelism currently works > > as follows: > > 1. Tasks are placed in a global shared queue. > > 2. Workers consume t

Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime

2019-06-05 Thread Janne Blomqvist
On Wed, Jun 5, 2019 at 9:25 PM 김규래 wrote: > > Hi, thanks for the detailed explanation. > I think I now get the picture. > Judging from my current understanding, the task-parallelism currently works > as follows: > 1. Tasks are placed in a global shared queue. > 2. Workers consume the tasks by bas

Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime

2019-06-05 Thread Jakub Jelinek
On Thu, Jun 06, 2019 at 03:25:24AM +0900, 김규래 wrote: > Hi, thanks for the detailed explanation. > I think I now get the picture. > Judging from my current understanding, the task-parallelism currently works > as follows: > 1. Tasks are placed in a global shared queue. It isn't a global shared qu

Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime

2019-06-05 Thread 김규래
Hi, thanks for the detailed explanation. I think I now get the picture. Judging from my current understanding, the task-parallelism currently works as follows: 1. Tasks are placed in a global shared queue. 2. Workers consume the tasks by bashing the queue in a while loop, just as self-scheduling

Re: Preventing ISO C errors when using macros for builtin types

2019-06-05 Thread Segher Boessenkool
On Wed, Jun 05, 2019 at 02:25:59PM +0100, Jozef Lawrynowicz wrote: > I'm assuming it would not be valid to modify the behaviour of __extension__ > so it can be placed within a declaration, and not just at the > beginning. However, there is minimal documentation on this keyword (it does > not > sta

sha512.sum for gcc-7.4.0.tar.gz incorrect on at least three mirrors

2019-06-05 Thread Farid Parpia
Greetings, It appears that the given sha512 sum for gcc-7.4.0.tar.gz may be incorrect on at least the following mirrors: http://mirrors.concertpass.com/ http://www.netgull.com/ https://bigsearcher.com/ Regards, Farid Parpia IBM Corporation: 710-2-RF28, 2455 South Road, Poughk

Preventing ISO C errors when using macros for builtin types

2019-06-05 Thread Jozef Lawrynowicz
The MSP430 target in the large memory model uses the (non-ISO) __int20 type for SIZE_TYPE and PTRDIFF_TYPE. The preprocessor therefore expands a builtin such as __SIZE_TYPE__ to "__int20 unsigned" in user code. When compiling with the "-pedantic-errors" flag, the use of any of these builtin macros

Re: About GSOC.

2019-06-05 Thread Tejas Joshi
Hello. Following patch is tested on following test cases in the testsuite and tests did not fail. I have considered most of the test cases this time hopefully. /* { dg-do link } */ extern int link_error (int); #define TEST(FN, VALUE, RESULT) \ if (__builtin_##FN (VALUE) != RESULT) link_error (

Re: On-Demand range technology [2/5] - Major Components : How it works

2019-06-05 Thread Richard Biener
On Tue, Jun 4, 2019 at 9:55 PM Andrew MacLeod wrote:> > On 6/4/19 1:07 PM, Richard Biener wrote: > > On June 4, 2019 6:50:07 PM GMT+02:00, Andrew MacLeod > > wrote: > >> On 6/4/19 11:37 AM, Richard Biener wrote: > >> > >>> where the single(!) query of the range of i on the alloca call > >>> will