public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] libgomp: Add tailing \n to gomp_debug Date: Thu, 28 Jul 2022 13:29:37 +0000 (GMT) [thread overview] Message-ID: <20220728132937.73E433856DFF@sourceware.org> (raw) https://gcc.gnu.org/g:89dd8390cdf18b02317b18edd4419b7b321b7040 commit 89dd8390cdf18b02317b18edd4419b7b321b7040 Author: Tobias Burnus <tobias@codesourcery.com> Date: Wed Jul 13 11:06:28 2022 +0200 libgomp: Add tailing \n to gomp_debug Contrary to gomp_{error,warning,fatal}, no tailing '\n' is added with gomp_debug; only affected was a 'requires'-related output. libgomp/ChangeLog: * target.c (gomp_target_init): Added tailing '\n' to gomp_debug. (cherry picked from commit 220bef460153a0296e947f16492d35e67b1b5b22) Diff: --- libgomp/ChangeLog.omp | 7 +++++++ libgomp/target.c | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp index fcd91098974..ef977cab3d3 100644 --- a/libgomp/ChangeLog.omp +++ b/libgomp/ChangeLog.omp @@ -1,3 +1,10 @@ +2022-07-13 Tobias Burnus <tobias@codesourcery.com> + + Backport from mainline: + 2022-07-12 Tobias Burnus <tobias@codesourcery.com> + + * target.c (gomp_target_init): Added tailing '\n' to gomp_debug. + 2022-07-08 Tobias Burnus <tobias@codesourcery.com> Backport from mainline: diff --git a/libgomp/target.c b/libgomp/target.c index 436547b97e7..997b2aa2f80 100644 --- a/libgomp/target.c +++ b/libgomp/target.c @@ -4498,7 +4498,7 @@ gomp_target_init (void) name[cur_len] = '\0'; gomp_debug (1, "%s devices present but 'omp requires %s' " - "cannot be fulfilled", name, buf); + "cannot be fulfilled\n", name, buf); free (name); } }
reply other threads:[~2022-07-28 13:29 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220728132937.73E433856DFF@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).