[Bug fortran/97009] Inlining with non-standard selected_int_kind leads to errors

2020-09-10 Thread pvitt at posteo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97009 --- Comment #1 from Peter Vitt --- I forgot to mention that we were able to reproduce this also with 10.1.0 and 9.3.0. In case this is of any help...

[Bug fortran/97009] New: Inlining with non-standard selected_int_kind leads to errors

2020-09-10 Thread pvitt at posteo dot de
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: pvitt at posteo dot de Target Milestone: --- Created attachment 49207 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49207&action=edit Minimum working example to reprod

[Bug fortran/87043] maybe-uninitialized warning for initialized variable

2018-08-22 Thread pvitt at posteo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87043 --- Comment #2 from Peter Vitt --- Oh, I see your point. But then still the question is why this warning is not shown when compiling with -Og.

[Bug fortran/87043] New: maybe-uninitialized warning for initialized variable

2018-08-21 Thread pvitt at posteo dot de
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: pvitt at posteo dot de Target Milestone: --- We have a MWE that provokes a "may be uninitialized" warning despite the value being initialized in all cases. Additionally, this warning is only created with