This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i
- From: Tobias Burnus <burnus at net-b dot de>
- To: Daniel Kraft <d at domob dot eu>
- Cc: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>, Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 01 Sep 2008 20:15:19 +0200
- Subject: Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i
- References: <48B961CD.8060606@domob.eu> <339c37f20808300905w11d0cc06x805f6d6c899ab32d@mail.gmail.com> <48B97648.4090705@domob.eu> <339c37f20808301016j4157ff60u54d45c9b0a50fe09@mail.gmail.com> <48B989DD.6010304@domob.eu> <48BB9B8C.9010209@net-b.de> <48BBD381.3000801@domob.eu> <339c37f20809010520g76f4010odd24548f0a5fce57@mail.gmail.com> <48BBF2F7.7080906@domob.eu>
Daniel Kraft wrote:
Committed as revision 139866 to trunk. If you want me to fix this on
4.3, too, you'll have to tell me if there's something I should know
for doing so :) I think I'll have to check-out
/branches/gcc-4_3-branch and do the fix there, too, right? Anything
special I should consider?
Nothing special, except that one should run "make check-gfortran" there
as well. Some people write in the patch's changelog "Backport from
mainline:" and then the date line from the mainline check in, but this
is not needed (cf. "ChangeLog"s there). And usually we (= gfortraners)
wait a week or so before checking into a branch to see whether a
regression on the trunk occur. I think your patch is simple enough that
one could do without the waiting, but you may prefer to wait still a few
days.
Tobias
- References:
- Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i
- Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i
- Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i
- From: Paul Richard Thomas
- Re: [Patch, Fortran] PR fortran/37193: USE m, ONLY: i, j => i