public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/106894] [13 regression] multiple libgomp failures after r13-2545-g9f2fca56593a2b
Date: Fri, 09 Sep 2022 11:47:23 +0000 [thread overview]
Message-ID: <bug-106894-4-RNX2L1Xypv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106894-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106894
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:26a1f4fcb264d110708483815c8c8d7bb4ff6788
commit r13-2559-g26a1f4fcb264d110708483815c8c8d7bb4ff6788
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Sep 9 13:43:43 2022 +0200
libgomp: Fix up OMP_PROC_BIND handling [PR106894]
While the first param is char (gomp_global_icv.bind_var), the second param
is char * (gomp_bind_var_list), so we shouldn't access it through *(char
*).
2022-09-09 Jakub Jelinek <jakub@redhat.com>
PR libgomp/106894
* env.c (initialize_env) <case PARSE_BIND>: Use char ** instead of
char * for dest[1] initialization from params[1]. Formatting
fixes.
next prev parent reply other threads:[~2022-09-09 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 22:48 [Bug libgomp/106894] New: " seurer at gcc dot gnu.org
2022-09-09 7:41 ` [Bug libgomp/106894] " rguenth at gcc dot gnu.org
2022-09-09 11:34 ` jakub at gcc dot gnu.org
2022-09-09 11:47 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-09 11:51 ` jakub at gcc dot gnu.org
2022-09-09 12:45 ` marcel at codesourcery dot com
2022-09-09 14:55 ` jakub at gcc dot gnu.org
2022-09-09 14:55 ` jakub at gcc dot gnu.org
2022-09-12 8:49 ` cvs-commit at gcc dot gnu.org
2022-09-12 9:14 ` jakub at gcc dot gnu.org
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=bug-106894-4-RNX2L1Xypv@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).