https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
--- Comment #7 from Steve Kargl ---
On Mon, Mar 23, 2020 at 02:41:23AM +, markwayne1969 at gmail dot com wrote:
>
> (In reply to Steve Kargl from comment #5)
> >
> > > Links to information about gcc development for this specific
> > > possi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
--- Comment #6 from Mark Paris ---
(In reply to Steve Kargl from comment #5)
> On Thu, Mar 19, 2020 at 10:24:10PM +, markwayne1969 at gmail dot com
> wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
> >
> > --- Comment #4 from M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
--- Comment #5 from Steve Kargl ---
On Thu, Mar 19, 2020 at 10:24:10PM +, markwayne1969 at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
>
> --- Comment #4 from Mark Paris ---
> (In reply to kargl from comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
--- Comment #4 from Mark Paris ---
(In reply to kargl from comment #3)
> No. Newer C, as opposed to older C, uses // for a comment.
> Fortran uses // as the concatenation operator. Run this
> through a cpp pre-processor.
>
> character(len=80)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
--- Comment #2 from Mark Paris ---
(In reply to Andrew Pinski from comment #1)
> gfortran defaults to -traditional-cpp preprocessor mode.
Thank you for your reply. If I may, I'd like to pose a question that I cannot
find the answer to from onlin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94228
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
