This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/81748] extensible types non-conforming behaviour
- From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 08 Aug 2017 17:27:30 +0000
- Subject: [Bug fortran/81748] extensible types non-conforming behaviour
- Auto-submitted: auto-generated
- References: <bug-81748-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81748
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-08-08
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Seems the output varies a bit. With current trunk, I get
the (also incorrect)
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
4195840
4195840
4
5
and valgrind tells me
ig25@linux-d6cw:/tmp> valgrind ./a.out
==3717== Memcheck, a memory error detector
==3717== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3717== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==3717== Command: ./a.out
==3717==
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
==3717== Conditional jump or move depends on uninitialised value(s)
==3717== at 0x40081F: __m_MOD_s (anton.f90:17)
==3717== by 0x400B8F: MAIN__ (anton.f90:30)
==3717== by 0x400D4E: main (anton.f90:22)
==3717==
==3717== Conditional jump or move depends on uninitialised value(s)
==3717== at 0x4E5560B: _gfortrani_gfc_itoa (string.c:191)
==3717== by 0x516FF7A: write_integer (write.c:1311)
==3717== by 0x5178CC5: list_formatted_write_scalar (write.c:1880)
==3717== by 0x517C1D4: _gfortrani_list_formatted_write (write.c:1958)
==3717== by 0x4008BA: __m_MOD_s (anton.f90:17)
==3717== by 0x400B8F: MAIN__ (anton.f90:30)
==3717== by 0x400D4E: main (anton.f90:22)
....