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

2018-04-03 Thread Peryt, Sebastian
Hi Martin, Frankly speaking I believe that students who discussed topics on mailing list might eventually just decide that they were too challenging for them and also competition appeared too difficult. As far as I remember student can only pick few organizations and maybe they just decided

Re: Patching the GCC build system to build MPICH and OpenCoarrays

2018-04-03 Thread Richard Biener
On Sat, Mar 31, 2018 at 2:44 AM, Damian Rouson wrote: > All, > > Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback on > our approach to patching the GCC build system to build MPICH and OpenCoarrays > after it builds gfortran (gfortran requires MPI and OpenCoarrays to sup

Re: where should C++ options be documented?

2018-04-03 Thread David Brown
On 03/04/18 03:33, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value, -Wconditionally-supported, > and -Wz

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

2018-04-03 Thread Martin Jambor
Hi Sebastian, On Tue, Apr 03 2018, Sebastian Peryt wrote: > Hi Martin, > > Frankly speaking I believe that students who discussed topics on mailing list > might > eventually just decide that they were too challenging for them and also > competition > appeared too difficult. As far as I remembe

Re: where should C++ options be documented?

2018-04-03 Thread Jason Merrill
On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value, -Wconditionally-supporte

Re: "file name" vs "filename"

2018-04-03 Thread Martin Sebor
On 04/01/2018 04:54 PM, Sandra Loosemore wrote: On 04/01/2018 02:56 PM, Joel Sherrill wrote: On Sun, Apr 1, 2018, 3:16 PM Gerald Pfeifer mailto:ger...@pfeifer.com>> wrote: And now to the most important question of all. ;-) Should we use "file name" or "filename" when referring to the

Re: where should C++ options be documented?

2018-04-03 Thread Martin Sebor
On 04/03/2018 08:08 AM, Jason Merrill wrote: On Mon, Apr 2, 2018 at 9:33 PM, Martin Sebor wrote: Jason, The manual mentions some C++-only options in the language independent section 3.8 Options to Request or Suppress Warnings and others in 3.5 Options Controlling C++ Dialect. For example, -Wc

Re: where should C++ options be documented?

2018-04-03 Thread Martin Sebor
On 04/03/2018 06:20 AM, David Brown wrote: On 03/04/18 03:33, Martin Sebor wrote: Jason, The manual mentions some C++-only options in the language independent section 3.8 Options to Request or Suppress Warnings and others in 3.5 Options Controlling C++ Dialect. For example, -Wcatch-value, -Wco

Re: Patching the GCC build system to build MPICH and OpenCoarrays

2018-04-03 Thread Damian Rouson
On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guent...@gmail.com) wrote: You probably only want a new target_module for the MPI library. Note  it's name has to match that of the directory containing the sources  which  as far as I see is 'mpich', not 'libmpi'.  Thanks!  I’ll ask Daniel

[wwwdocs] PATCH for Re: Remove *.mirror.babylon.network

2018-04-03 Thread Gerald Pfeifer
On Wed, 21 Mar 2018, Tim Semeijn wrote: > For the foreseeable future we will not be able to provide our mirrors > anymore. Could you please remove: > > nl.mirror.babylon.network > fr.mirror.babylon.network Thank you for letting us know, Tim, and your service in the past! Both are really appreciat