From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24461 invoked by alias); 18 Oct 2015 12:00:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 23960 invoked by uid 48); 18 Oct 2015 12:00:08 -0000 From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/68009] New: [6 Regression] prototype for gfortran_runtime_error with inline matmul Date: Sun, 18 Oct 2015 12:00: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: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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 target_milestone Message-ID: 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: 2015-10/txt/msg01411.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68009 Bug ID: 68009 Summary: [6 Regression] prototype for gfortran_runtime_error with inline matmul Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: tkoenig at gcc dot gnu.org Target Milestone: --- A discussion from the gfortran mailing list that never made it into Bugzilla... See the thread at https://gcc.gnu.org/ml/fortran/2015-07/msg00079.html . The declaration of gfortran_runtime_error as emitted by the FE is incorrect, it does not take into account that it is variadic. This is incorrect, and causes actual problems on nvptx. A simplistic solution which sets resolved_isym on the symbol introduces even stranger behavior: The function call is optimized away completele (see https://gcc.gnu.org/ml/fortran/2015-07/msg00127.html ).