https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90889
--- Comment #5 from Jan Hubicka <hubicka at ucw dot cz> --- > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90889 > > Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > Last reconfirmed| |2019-06-16 > Ever confirmed|0 |1 > > --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > > BTW are all those type mismatch waning actually correct? I was looking into > > the Ada manual for C compatibility and i think we implement it correctly, so > > there should be no mismatches if language standard is followed. It is easily > > possible that I missed something important. > > Most warnings are in units implementing the low-level support of the language, > in particular exceptions, so this is not pure Ada. A few others could be > fixed. Perhaps it may make sense to compile the non-compliant units with -fno-lto so we stay safe? > > > BTW -fchecking=0 lets me to finish the build, but later I get wrong -fPIC > > for ada runtime, which also seem new. > > You probably need to restart the build of the runtime after removing the > various timestamps in $(builddir)/gcc and $(builddir)/$(target)/libada. Will try :) (while working on alias oracle I would like to be able to LTO test Ada since it has some specialities in this area) Honza
