[Info-vax] [OT?] Should compiler warnings be treated as errors ?
John Reagan
xyzzy1959 at gmail.com
Mon Sep 13 16:42:39 EDT 2021
On Monday, September 13, 2021 at 1:53:35 PM UTC-4, Simon Clubley wrote:
> On 2021-09-13, John Reagan <xyzz... at gmail.com> wrote:
> > On Sunday, September 12, 2021 at 9:04:00 AM UTC-4, Simon Clubley wrote:
> >>
> >> OTOH, going the other way, I wonder if the LLVM compilers (with the
> >> normal LLVM frontends instead of hybrid GEM frontend/LLVM backend)
> >> will find things in the VMS source code that DEC C might have missed.
> >
> > Compiler(S) plural?
> >
> Yes, although I should have expanded on the explicit reference to DEC C.
> Don't you have Fortran code within the VMS code base ?
No. There is some in the automated testing environment however.
>
> I did think of Pascal as well but I don't think there's a production-ready
> Pascal frontend for LLVM, although Free Pascal appears to be doing some
> initial work with LLVM.
> > Are you asking could we take OpenVMS C source code and run it through the clang
> > compiler in "C mode"? That probably won't work in general as the code often uses
> > features not in clang (#pragma linkage, /STANDARD=VAXC, etc.). There might
> > be some C code that doesn't rely on such things that could be compiled with
> > "clang-in-C-mode" but I haven't thought that far into the future.
> >
> Yes, that's what I was thinking of, and the same for any Fortran code
> as well as any Pascal code _if_ there turned out to be a version of
> Pascal for LLVM after all that supports the VMS Pascal syntax.
> Simon.
>
> --
> Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
> Walking destinations on a map are further away than they appear.
I don't get all the hate for the GEM-to-CIL converter. Compilers are full of transformations
between intermediate forms. What are you worried about?
More information about the Info-vax
mailing list