Dave Korn wrote:
> Tobias Burnus wrote:
>
>> I have another idea: Just handle "PROGRAM main" specially by using the
>> name "MAIN__". It should be still quite readable in the middle-end
>> diagnostics. Furthermore, it matches the assembler name and using "b
>> main" one still get something useful - and it is less confusing for
>> everyone (middle end, users of -fdump-tree-original etc.) if there is
>> only a single "main".
>
> Okeydokey. I'm running this through the fortran+gomp testsuite. No
> problems so far.
Clean sweep on fortran:
> === gfortran Summary ===
>
> # of expected passes 30176
> # of expected failures 19
> # of unsupported tests 289
> /gnu/gcc/obj-patched2b/gcc/testsuite/gfortran/../../gfortran version 4.5.0
> 20090528 (experimental) (GCC)
No regressions (a handful of pre-existing failures) on libgomp:
> === libgomp Summary ===
>
> # of expected passes 2400
> # of unexpected failures 4
> # of unsupported tests 2
> runtest completed at Sun May 31 13:39:24 2009
I reckon you should apply the patch and we can close PR40309. Thanks for
all the help :)
cheers,
DaveK
