Fwd: 10% runtime regression in rnflow Polyhedron benchmark
-- Forwarded message -- From: Sergey Ostanevich Date: Wed, Sep 26, 2012 at 4:55 PM Subject: Re: 10% runtime regression in rnflow Polyhedron benchmark To: Dominique Dhumieres On Mon, Sep 17, 2012 at 1:18 PM, Dominique Dhumieres wrote: > Hi Uros, > >> Recent patch introduced 10% runtime regression on x86_64 targets in >> rnflow Polyhedron benchmark [1]. Did somebody alread bisected to the >> offending patch? > > I see it since some time. It is on my TODO list to open a new PR. > You can suppress the slowdown with -fno-tree-loop-if-convert. > > I think I have already done the bissection, but right now I am > chasing another problem and I'll need a couple hours to get to > it. > commit 024fee2c369096e6fe6cde620243df5843893004 Author: rguenth Date: Thu Sep 13 12:43:58 2012 + PR54717 filed regards, Sergos
Steering Committee: I propose Cary Coutant as DWARF maintainer
I propose that Cary Coutant become an additional DWARF maintainer, along with Jason. Cary has been on the DWARF working group for many years and is very familiar with the format. He has written several patches for GCC's DWARF code. He's been an extensive contributor to the gold linker. I suggest that Cary be listed as "dwarf debugging code" in the MAINTAINERs file, like Jason. The exact meaning of this is not spelled out in the file, but presumably includes the right to review, approve and commit patches to gcc/dwarf*.[ch] and associated files in the include directory. I'd like the steering committee to consider this proposal. Thanks. Ian
Re: Steering Committee: I propose Cary Coutant as DWARF maintainer
+1 from me --joel Ian Lance Taylor wrote: >I propose that Cary Coutant become an additional >DWARF maintainer, along with Jason. Cary has been on the DWARF >working group for many years and is very familiar with the format. He >has written several patches for GCC's DWARF code. He's been an >extensive contributor to the gold linker. > >I suggest that Cary be listed as "dwarf debugging code" in the >MAINTAINERs file, like Jason. The exact meaning of this is not >spelled out in the file, but presumably includes the right to review, >approve and commit patches to gcc/dwarf*.[ch] and associated files in >the include directory. > >I'd like the steering committee to consider this proposal. > >Thanks. > >Ian
Re: Steering Committee: I propose Cary Coutant as DWARF maintainer
On 09/26/2012 06:27 PM, Ian Lance Taylor wrote: I propose that Cary Coutant become an additional DWARF maintainer, along with Jason. That makes sense to me. Jason
Re: Steering Committee: I propose Cary Coutant as DWARF maintainer
On 09/26/2012 03:27 PM, Ian Lance Taylor wrote: I propose that Cary Coutant become an additional DWARF maintainer, along with Jason. Cary has been on the DWARF working group for many years and is very familiar with the format. He has written several patches for GCC's DWARF code. He's been an extensive contributor to the gold linker. I suggest that Cary be listed as "dwarf debugging code" in the MAINTAINERs file, like Jason. The exact meaning of this is not spelled out in the file, but presumably includes the right to review, approve and commit patches to gcc/dwarf*.[ch] and associated files in the include directory. I'd like the steering committee to consider this proposal. I'm happy to recommend Cary as DWARF maintainer. -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077