On Mon, Oct 24, 2016 at 10:47 PM, Jerry DeLisle <jvdeli...@charter.net> wrote: > On 10/24/2016 07:23 AM, Fritz Reese wrote: >> >> https://gcc.gnu.org/ml/fortran/2016-10/msg00087.html et. al. >>> >>> On 12/10/16 13:30, Fritz Reese wrote: >>>> >>>> Here I submit for review four small extensions to the GNU Fortran >>>> frontend for compatibility with legacy code. I figure it might be a >>>> nice change of pace from my larger patches. Never fear, for I have >>>> more large patches to come, which I will continue to submit >>>> one-at-a-time. ... >> OK for trunk now? (regtests x86_64-redhat-linux) >> > > God do go! > > Jerry >
Committed r241516, r241517, r241518, r241519. --- Fritz Reese --- Fritz Reese On Mon, Oct 24, 2016 at 10:47 PM, Jerry DeLisle <jvdeli...@charter.net> wrote: > On 10/24/2016 07:23 AM, Fritz Reese wrote: >> >> https://gcc.gnu.org/ml/fortran/2016-10/msg00087.html et. al. >>> >>> On 12/10/16 13:30, Fritz Reese wrote: >>>> >>>> Here I submit for review four small extensions to the GNU Fortran >>>> frontend for compatibility with legacy code. I figure it might be a >>>> nice change of pace from my larger patches. Never fear, for I have >>>> more large patches to come, which I will continue to submit >>>> one-at-a-time. >> >> >> Sorry I took a break from this last week. Back on it this week. I >> really hope I can get the rest of my major extensions in before the >> next release stage, which is apparently imminent, so I might have an >> overwhelming number of submissions this week... >> >> Here's how I'm thinking of the flags situation: we use -std=legacy for >> old compatibility stuff that users shouldn't use, and -fdec for >> ancient compatibility stuff that users _really_ shouldn't use. So if a >> user wants the compiler to mimic an old DEC compiler they hit -fdec >> and get -std=legacy and all the bells and whistles of the >> deleted/obsolete/compatibility extensions without question. Otherwise >> they can just use -std=legacy for a more reasonable compilation, or >> -std=gnu for some such extensions with reasonable warnings. >> >> Anyway, here's a resubmission of the several patches for the four >> extensions mentioned previously, plus an initial cleanup patch for >> -fdec. Sorry to pork-barrel the cleanup patch in here, but it combines >> some stuff I've been meaning to touch up with the change of making >> -fdec into flag_dec using Fortran Var. (This is necessary for the >> type-print and future extensions to be enabled with -fdec without >> their own flag.) >> >> To summarize, we have >> 0001 Cleanup -fdec: rolls some options in with fdec that were >> documented as being a part of it previously (-fdollar-ok, >> -fcray-pointer, -fd-lines-as-comments, legacy/deleted/obsolete feature >> standard bits) and moves fdec-structure out of gfc_option to use >> Fortran Var. >> 0002 [always] Form feed: feed characters ('\f') accepted as whitespace in >> source >> 0003 [-fdec] TYPE is an alias for PRINT >> 0004 [-std=legacy] %LOC() can be used as an rval (like the LOC() >> intrinsic) >> 0005 [-std=legacy] Support for .XOR. operator (same as .NEQV.) >> >> The -std=legacy extensions of course compile clean with -std=legacy, >> give warnings with-std=gnu, and give errors with -std=f*. >> >> OK for trunk now? (regtests x86_64-redhat-linux) >> > > God do go! > > Jerry >
