From: Martin Jambor <mjambor@suse.cz>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: vries@gcc.gnu.org, "Thomas König" <tk@tkoenig.net>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PR85463 '[nvptx] "exit" in offloaded region doesn't terminate process'
Date: Thu, 26 Apr 2018 12:39:00 -0000 [thread overview]
Message-ID: <ri6604e2ld7.fsf@suse.cz> (raw)
In-Reply-To: <87zi1q9rd5.fsf@hertz.schwinge.homeip.net>
Hi,
On Thu, Apr 26 2018, Thomas Schwinge wrote:
> Hi Martin!
>
> On Wed, 25 Apr 2018 15:56:26 +0200, Martin Jambor <mjambor@suse.cz> wrote:
>> On Thu, Apr 19 2018, Thomas Schwinge wrote:
>> > * testsuite/libgomp.oacc-fortran/error_stop-1.f: New file.
>> > * testsuite/libgomp.oacc-fortran/error_stop-2.f: Likewise.
>> > * testsuite/libgomp.oacc-fortran/error_stop-3.f: Likewise.
>> > * testsuite/libgomp.oacc-fortran/stop-1.f: Likewise.
>> > * testsuite/libgomp.oacc-fortran/stop-2.f: Likewise.
>> > * testsuite/libgomp.oacc-fortran/stop-3.f: Likewise.
>>
>> The "output pattern test" part of all of these new testcases fail on my
>> HSA tester even though no HSAIL is generated for them
>
>
> Is there anything "special" in your HSA machine regarding stdout/stderr?
> How are you testing GCC there: native testing or some non-standard *.exp
> file, for example? Does using strace give any idea where which part of
> the output is going?
>
this issue was caused on my side, because the ROCm runtime produced some
debug output to stderr upon initialization. I have backported a fix for
this to my packages and the issues is gone.
It is still slightly intriguing, because the patterns dg-output was
searching for were present there also before, the debug stuff did not
appear in the middle of them or anything, so I do not quite understand
why the tests were failing before, but it is probably not worth
investigating. Let's hope the periodic run next week will agree with my
manual tests.
Sorry for the noise,
Martin
next prev parent reply other threads:[~2018-04-26 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 9:30 [patch, libfortran, committed] Implement stop_numeric for minimal targets Thomas König
2018-04-19 9:06 ` PR85463 '[nvptx] "exit" in offloaded region doesn't terminate process' (was: [patch, libfortran, committed] Implement stop_numeric for minimal targets) Thomas Schwinge
2018-04-19 9:36 ` Jakub Jelinek
2018-04-19 9:19 ` Thomas Schwinge
2018-04-19 9:25 ` Jakub Jelinek
2018-04-19 9:36 ` Thomas Schwinge
2018-04-19 11:32 ` Thomas König
2018-04-19 11:59 ` Thomas Schwinge
2018-04-19 17:59 ` PR85463 '[nvptx] "exit" in offloaded region doesn't terminate process' Thomas König
2018-04-25 13:56 ` PR85463 '[nvptx] "exit" in offloaded region doesn't terminate process' (was: [patch, libfortran, committed] Implement stop_numeric for minimal targets) Martin Jambor
2018-04-26 10:47 ` PR85463 '[nvptx] "exit" in offloaded region doesn't terminate process' Thomas Schwinge
2018-04-26 12:39 ` Martin Jambor [this message]
[not found] ` <20230119220005.2002779-1-thomas@codesourcery.com>
2023-01-20 20:12 ` Clean up after newlib "nvptx: In offloading execution, map '_exit' to 'abort' [GCC PR85463]" Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ri6604e2ld7.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.com \
--cc=tk@tkoenig.net \
--cc=vries@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).