public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug testsuite/96212] New: new test case libgomp.fortran/alloc-3.F fails in r11-2101 @ 2020-07-15 20:24 seurer at linux dot vnet.ibm.com 2020-07-15 20:43 ` [Bug testsuite/96212] " seurer at linux dot vnet.ibm.com 2020-07-15 21:10 ` burnus at gcc dot gnu.org 0 siblings, 2 replies; 3+ messages in thread From: seurer at linux dot vnet.ibm.com @ 2020-07-15 20:24 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96212 Bug ID: 96212 Summary: new test case libgomp.fortran/alloc-3.F fails in r11-2101 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at linux dot vnet.ibm.com Target Milestone: --- g:fff15bad1ab571906c37b88380431768d917dcb0, r11-2101 make -k check-target-libgomp RUNTESTFLAGS=fortran.exp=libgomp.fortran/alloc-3.F FAIL: libgomp.fortran/alloc-3.F -O execution test # of expected passes 1 # of unexpected failures 1 spawn [open ...] STOP 4 FAIL: libgomp.fortran/alloc-3.F -O execution test testcase /home/seurer/gcc/git/gcc-test/libgomp/testsuite/libgomp.fortran/fortran.exp completed in 1 seconds ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug testsuite/96212] new test case libgomp.fortran/alloc-3.F fails in r11-2101 2020-07-15 20:24 [Bug testsuite/96212] New: new test case libgomp.fortran/alloc-3.F fails in r11-2101 seurer at linux dot vnet.ibm.com @ 2020-07-15 20:43 ` seurer at linux dot vnet.ibm.com 2020-07-15 21:10 ` burnus at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: seurer at linux dot vnet.ibm.com @ 2020-07-15 20:43 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96212 --- Comment #1 from Bill Seurer <seurer at linux dot vnet.ibm.com> --- After running on a few more machines this appears to be a BE only issue. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug testsuite/96212] new test case libgomp.fortran/alloc-3.F fails in r11-2101 2020-07-15 20:24 [Bug testsuite/96212] New: new test case libgomp.fortran/alloc-3.F fails in r11-2101 seurer at linux dot vnet.ibm.com 2020-07-15 20:43 ` [Bug testsuite/96212] " seurer at linux dot vnet.ibm.com @ 2020-07-15 21:10 ` burnus at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: burnus at gcc dot gnu.org @ 2020-07-15 21:10 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96212 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Bill Seurer from comment #1) > After running on a few more machines this appears to be a BE only issue. alloc-1.F90 uses a proper interface (Fortran module). alloc-3.F uses a header file with the old-style Fortran 66/77 way of just having external subroutine_name or external function_name integer function_name ! <- data type the function returns. Thus, by this declaration the compiler does not know how the interface actually looks like. In principle, it could (and should?!?) deduce the interface from the first procedure call – and create the declaration from the use. However, it doesn't do this. My bet is that the actually used argument-passing of caller and callee differs on PowerPC and, hence, it fails. Solution? * XFAIL? * Changing the way in gfortran how the external-function declaration is generated? ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-07-15 21:10 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-07-15 20:24 [Bug testsuite/96212] New: new test case libgomp.fortran/alloc-3.F fails in r11-2101 seurer at linux dot vnet.ibm.com 2020-07-15 20:43 ` [Bug testsuite/96212] " seurer at linux dot vnet.ibm.com 2020-07-15 21:10 ` burnus at gcc dot gnu.org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).