Re: Status of m32c target?

> It's a bit like writing a new backend, except you have all this existing > code to worry about as well. Unless you start from scratch (which may > not be such a bad idea: you get to modernise it all, and it isn't _really_ > from scratch, you can peek at the old code and copy stuff from it). I d

Re: Bugzilla timing out

On Mon, Jan 22, 2018 at 7:08 PM, Frank Ch. Eigler wrote: > Hi - > >> Problems are still occurring for me; Bugzilla gives me 504 Gateway >> Time-outs when I try to access it tonight... > > OK, we reworked some of the database routine maintenance workload, > e.g., a nightly cleanup pass that was qui

Re: Google Summer of Code 2018: Call for mentors and ideas

Hi, On Wed, Jan 17 2018, Martin Jambor wrote: > Hi, > > following a discussion at IRC about an upcoming deadline to register GCC > as an independent organization for Google Summer of Code 2018 (GSoC), I > have volunteered to serve as the org-admin for GCC if: > > - there is not another volunteer

Re: Google Summer of Code 2018: Call for mentors and ideas

On 23 January 2018 at 16:26, Martin Jambor wrote: > Hi, > > On Wed, Jan 17 2018, Martin Jambor wrote: >> Hi, >> >> following a discussion at IRC about an upcoming deadline to register GCC >> as an independent organization for Google Summer of Code 2018 (GSoC), I >> have volunteered to serve as the

Re: Bugzilla timing out

Hi - On Tue, Jan 23, 2018 at 11:26:42AM +0100, Richard Biener wrote: > [...] > > OK, we reworked some of the database routine maintenance workload, > > e.g., a nightly cleanup pass that was quite likely excessive, and > > will keep monitoring. > > With all such administrative workloads keep in mi

Re: Google Summer of Code 2018: Call for mentors and ideas

On 01/23/2018 12:08 PM, Prathamesh Kulkarni wrote: > On 23 January 2018 at 16:26, Martin Jambor wrote: >> Hi, >> >> On Wed, Jan 17 2018, Martin Jambor wrote: >>> Hi, >>> >>> following a discussion at IRC about an upcoming deadline to register GCC >>> as an independent organization for Google Summe

Different dynamical array debug info 7.2 vs. 8.0

Hi, I observed that gfortran 7.2 and 8.0 generate different debug info for dynamical array. Here is a case simplified from gdb test case gdb.fortran/vla-datatypes.f90 $ cat vla-datatypes.f90 program vla_primitives integer, allocatable:: intvla(:, :, :) logical :: l al

Re: Google Summer of Code 2018: Call for mentors and ideas

Hi, On Tue, Jan 23 2018, Prathamesh Kulkarni wrote: > On 23 January 2018 at 16:26, Martin Jambor wrote: >> Hi, >> >> On Wed, Jan 17 2018, Martin Jambor wrote: >>> Hi, >>> >>> following a discussion at IRC about an upcoming deadline to register GCC >>> as an independent organization for Google Sum