On Fri, May 4, 2018 at 9:22 AM, Bert Wesarg
wrote:
> Hi,
>
> On Wed, May 2, 2018 at 2:15 PM, Jakub Jelinek wrote:
> > Some code that compiled successfully with older GCC versions might
> require
> > source changes, see http://gcc.gnu.org/gcc-8/porting_to.html for
> > details.
>
> in "Fortran lan
Hi,
On Wed, May 2, 2018 at 2:15 PM, Jakub Jelinek wrote:
> Some code that compiled successfully with older GCC versions might require
> source changes, see http://gcc.gnu.org/gcc-8/porting_to.html for
> details.
in "Fortran language issues" it reads: "Prior to GCC 7", shouldn't
that be "Prior to
On 05/02/2018 10:21 AM, Damian Rouson wrote:
Could someone please point me to instructions for how to submit a change to the
gfortran changes list? I’d like to add the following bullet:
See also
https://gcc.gnu.org/contribute.html#webchanges
Jim
On 2 May 2018 at 18:21, Damian Rouson wrote:
> Could someone please point me to instructions for how to submit a change to
> the gfortran changes list?
The web pages are hosted in CVS and patches for them are handled like
any other GCC patches:
https://gcc.gnu.org/about.html#cvs
On May 2, 2018 at 9:43:23 AM, Jakub Jelinek
(ja...@redhat.com(mailto:ja...@redhat.com)) wrote:
> There is no deadline on gcc-*/changes.html changes, it can be changed
> whenever changes for it are acked. Of course it is always better to
> do it before the release if possible.
>
Could some
On Wed, May 02, 2018 at 11:38:51AM -0500, Daniel Santos wrote:
> Looks like I forgot to add the details of -mcall-ms2sysv-xlogues to the
> changes (https://gcc.gnu.org/gcc-8/changes.html). Is it too late to
> change that? At least this only really affects one project (that I'm
> aware of). I've
Woo hoo!
Looks like I forgot to add the details of -mcall-ms2sysv-xlogues to the
changes (https://gcc.gnu.org/gcc-8/changes.html). Is it too late to
change that? At least this only really affects one project (that I'm
aware of). I've got some improvements to it for GCC 9 that I'll get
together
