From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-471836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5473 invoked by alias); 29 Dec 2014 10:44:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 5450 invoked by uid 48); 29 Dec 2014 10:44:28 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64432] New: [5 Regression] SYSTEM_CLOCK(COUNT_RATE=rate) wrong result for integer(4)::rate
Date: Mon, 29 Dec 2014 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-64432-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg02843.txt.bz2

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

            Bug ID: 64432
           Summary: [5 Regression] SYSTEM_CLOCK(COUNT_RATE=rate) wrong
                    result for integer(4)::rate
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: anlauf at gmx dot de

I just discovered that the 20141227 snapshot breaks SYSTEM_CLOCK when
the COUNT_RATE argument is a 32-bit integer:

% cat gfcbug128.f90
program gfcbug128
  integer(4) :: count_rate, count_max
  call system_clock (count_rate=count_rate)
  call system_clock (count_max=count_max)
  print *, count_rate, count_max
end

GNU Fortran (GCC) 5.0.0 20141227 (experimental)
produces:

% head -11 gfcbug128.f90.003t.original
gfcbug128 ()
{
  integer(kind=4) count_max;
  integer(kind=4) count_rate;

  {
    integer(kind=8) count_rate.0;

    _gfortran_system_clock_8 (0B, &count_rate.0, 0B);
    count_rate = (integer(kind=4)) count_rate.0;
    _gfortran_system_clock_4 (0B, 0B, &count_max);

whereas my 4.9 or other older installations give:

% head -7 gfcbug128.f90.003t.original-49 
gfcbug128 ()
{
  integer(kind=4) count_max;
  integer(kind=4) count_rate;

  _gfortran_system_clock_4 (0B, &count_rate, 0B);
  _gfortran_system_clock_4 (0B, 0B, &count_max);

On my Linux system, the _4 version has count_rate=1000,
the _8 version is 1000000.

:-(