[Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT

["ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760

--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> OH!  I thought you meant here.  I wasn't sure this was the same bug
> internally.  They have different results in the two different versions of
> GNAT.  The AdaCore GNAT Community put out a crash report while the FSF GNAT
> only returned quietly with no compilation results.

Here's what I get:

eric@polaris:~/build/gcc/native> ~/install/gcc-7-branch/bin/gcc -c main.adb 
+===========================GNAT BUG DETECTED==============================+
| 7.3.1 20180407 [gcc-7-branch revision 259208] (x86_64-suse-linux)        |
| Storage_Error stack overflow or erroneous memory access                  |
| Error detected at main.adb:11:4                                          |
| Please submit a bug report; see https://gcc.gnu.org/bugs/ .              |

eric@polaris:~/build/gcc/native> ~/install/gcc-8-branch/bin/gcc -c main.adb 
eric@polaris:~/build/gcc/native>

> I've seen multiple times in the past where a bug was fixed in a earlier 
> version of GNAT GPL/Community but not in a later version of FSF GNAT, which
> probably means they weren't actually the same bug internally.

The chance that the same code triggers 2 different bugs in the compiler is
virtually zero; what you experienced is only a discrepancy in release cycles.

> Also there is no guarantee they'll even look at my report as it was for the 
> community edition (this is not a knock against them, they have their own 
> priorities that they must manage first).   I was just trying to be nice to 
> help them find bugs as well.  I wasn't meaning to cause trouble, just help 
> contribute to making GNAT the best it can be in all versions.  

There is a single GNAT codebase so there is no need to duplicate bug reports
for all the different variants, they will eventually be resynced at some point.

> So my apologies on the trouble.  I was not intending to cause any.  I hope
> you will forgive me.

Not sure if there is anything to forgive given your explanation.