https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80484
--- Comment #9 from Walt Brainerd <walt.brainerd at gmail dot com> --- Just FYI, Intel 2017 compiles 3DT'...', but it does not run correctly (response inspired by your comments about a similar possibility :-). On Sat, Apr 22, 2017 at 12:35 PM, jvdelisle at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80484 > > --- Comment #7 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- > Created attachment 41246 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41246&action=edit > Preliminary patch for testing > > This patch takes care of the rejected format with a repeat in front of the > DT > and the '/' inserted after. I am still testing and exploring the business > with > the USE statement. > > Note: I have not checked to make sure the runtime also handles the repeat > correctly. This is a work in progress. I am suspicious of this patch > since I > expected the unget_char to be sufficient and the lexing would cycle around > and > catch that '/'. Obviously it does not, but I do want to understand why > not. I > do understand why the repeat digit was missed and that part is good. > (Helps if > you put the new code in the right place, ;) ) > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.