public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] Merge branch 'master' into devel/sphinx
Date: Tue, 10 Aug 2021 07:12:42 +0000 (GMT) [thread overview]
Message-ID: <20210810071242.36F583951C83@sourceware.org> (raw)
https://gcc.gnu.org/g:7d5bfcbfd3f9074e48e78b82c60d9b5aca5011a0
commit 7d5bfcbfd3f9074e48e78b82c60d9b5aca5011a0
Merge: 9207fa3effc 0631faf87a1
Author: Martin Liska <mliska@suse.cz>
Date: Tue Aug 10 09:12:21 2021 +0200
Merge branch 'master' into devel/sphinx
Diff:
ChangeLog | 4 +
gcc/ChangeLog | 123 ++
gcc/DATESTAMP | 2 +-
gcc/Makefile.in | 2 +-
gcc/builtins.def | 8 +-
gcc/c/c-typeck.c | 2 +-
gcc/common.opt | 2 +-
gcc/config/aarch64/aarch64-simd.md | 15 +-
gcc/config/aarch64/aarch64.md | 2 +-
gcc/config/gcn/gcn-protos.h | 5 +-
gcc/config/gcn/gcn-tree.c | 58 +-
gcc/config/gcn/gcn.c | 21 +-
gcc/config/gcn/gcn.opt | 5 -
gcc/config/i386/constraints.md | 10 +-
gcc/config/i386/i386.c | 11 +-
gcc/config/i386/mmx.md | 2 +-
gcc/config/i386/predicates.md | 4 +
gcc/config/i386/sse.md | 47 +-
gcc/config/nvptx/nvptx.c | 5 +
gcc/config/rs6000/rs6000.c | 14 +-
gcc/doc/gty.texi | 5 +-
gcc/doc/tm.texi | 9 +
gcc/doc/tm.texi.in | 2 +
gcc/gimple-range-fold.cc | 6 +
gcc/ipa-prop.c | 2 +-
gcc/omp-builtins.def | 11 +-
gcc/omp-low.c | 2 +
gcc/omp-oacc-neuter-broadcast.cc | 1522 ++++++++++++++++++++
gcc/optc-gen.awk | 8 +-
gcc/opts.c | 6 +-
gcc/passes.def | 1 +
gcc/target.def | 11 +
gcc/testsuite/ChangeLog | 67 +
gcc/testsuite/g++.dg/ipa/pure-const-3.C | 2 +-
gcc/testsuite/gcc.dg/ipa/remref-6.c | 2 +-
gcc/testsuite/gcc.dg/pr101741.c | 16 +
gcc/testsuite/gcc.dg/pr68217.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/vrp24.c | 2 +-
gcc/testsuite/gcc.dg/vla-stexp-1.c | 18 +
.../gcc.target/aarch64/vect-shr-reg-run.c | 53 +
gcc/testsuite/gcc.target/aarch64/vect-shr-reg.c | 30 +
gcc/testsuite/gcc.target/i386/avx2-gather-2.c | 3 +-
gcc/testsuite/gcc.target/i386/cond_op_shift_d-1.c | 56 +
gcc/testsuite/gcc.target/i386/cond_op_shift_d-2.c | 102 ++
gcc/testsuite/gcc.target/i386/cond_op_shift_q-1.c | 11 +
gcc/testsuite/gcc.target/i386/cond_op_shift_q-2.c | 5 +
gcc/testsuite/gcc.target/i386/cond_op_shift_ud-1.c | 10 +
gcc/testsuite/gcc.target/i386/cond_op_shift_ud-2.c | 5 +
gcc/testsuite/gcc.target/i386/cond_op_shift_uq-1.c | 10 +
gcc/testsuite/gcc.target/i386/cond_op_shift_uq-2.c | 5 +
gcc/testsuite/gcc.target/i386/cond_op_shift_uw-1.c | 8 +
gcc/testsuite/gcc.target/i386/cond_op_shift_uw-2.c | 6 +
gcc/testsuite/gcc.target/i386/cond_op_shift_w-1.c | 8 +
gcc/testsuite/gcc.target/i386/cond_op_shift_w-2.c | 6 +
gcc/testsuite/gcc.target/i386/pr101812.c | 12 +
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_1.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_10.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_11.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_12.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_15.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_16.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_17.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_18.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_3.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_5.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_6.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_7.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_8.c | 2 +-
gcc/testsuite/gfortran.dg/ISO_Fortran_binding_9.c | 2 +-
gcc/testsuite/gfortran.dg/PR94327.c | 2 +-
gcc/testsuite/gfortran.dg/PR94331.c | 2 +-
.../gfortran.dg/bind_c_array_params_3_aux.c | 2 +-
.../iso_fortran_binding_uint8_array_driver.c | 2 +-
gcc/testsuite/gfortran.dg/pr93524.c | 2 +-
gcc/testsuite/lib/gfortran.exp | 10 +-
gcc/tree-pass.h | 1 +
gcc/tree-ssa-ccp.c | 118 +-
libgomp/ChangeLog | 18 +
libgomp/plugin/plugin-gcn.c | 3 +-
.../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c | 3 -
.../libgomp.oacc-c-c++-common/loop-dim-default.c | 4 +-
.../libgomp.oacc-c-c++-common/parallel-dims.c | 12 +-
.../libgomp.oacc-c-c++-common/routine-wv-2.c | 7 +-
.../libgomp.oacc-fortran/optional-reduction.f90 | 3 +
.../testsuite/libgomp.oacc-fortran/reduction-7.f90 | 3 +
libstdc++-v3/ChangeLog | 28 +
libstdc++-v3/include/bits/regex.h | 28 +-
libstdc++-v3/include/bits/regex.tcc | 6 +-
libstdc++-v3/include/bits/regex_automaton.tcc | 4 +-
libstdc++-v3/include/bits/regex_compiler.h | 8 +-
libstdc++-v3/include/bits/regex_executor.h | 6 +-
libstdc++-v3/include/debug/safe_container.h | 13 +-
libstdc++-v3/include/std/regex | 3 +
.../23_containers/unordered_map/cons/default.cc | 3 +
.../23_containers/unordered_set/cons/default.cc | 3 +
95 files changed, 2514 insertions(+), 174 deletions(-)
diff --cc gcc/doc/tm.texi
index 7de33b9e344,a30fdcbbf3d..3e12ddf36b9
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@@ -6813,8 -6408,16 +6813,17 @@@ Only define this hook if your accelerat
private variables at OpenACC device-lowering time using the
@code{TARGET_GOACC_ADJUST_PRIVATE_DECL} target hook.
@end deftypefn
+@c hook-end
+ @deftypefn {Target Hook} tree TARGET_GOACC_CREATE_WORKER_BROADCAST_RECORD (tree @var{rec}, bool @var{sender}, const char *@var{name})
+ Create a record used to propagate local-variable state from an active
+ worker to other workers. A possible implementation might adjust the type
+ of REC to place the new variable in shared GPU memory.
+
+ Presence of this target hook indicates that middle end neutering/broadcasting
+ be used.
+ @end deftypefn
+
@node Anchored Addresses
@section Anchored Addresses
@cindex anchored addresses
next reply other threads:[~2021-08-10 7:12 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 7:12 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 11:37 Martin Liska
2022-11-07 8:55 Martin Liska
2022-11-07 7:25 Martin Liska
2022-10-28 8:02 Martin Liska
2022-10-26 10:59 Martin Liska
2022-10-21 10:48 Martin Liska
2022-10-19 13:25 Martin Liska
2022-10-17 8:20 Martin Liska
2022-10-15 13:33 Martin Liska
2022-10-13 13:54 Martin Liska
2022-10-08 8:19 Martin Liska
2022-10-04 10:05 Martin Liska
2022-09-29 8:41 Martin Liska
2022-09-26 19:06 Martin Liska
2022-09-20 15:24 Martin Liska
2022-09-20 12:03 Martin Liska
2022-09-20 11:53 Martin Liska
2022-09-12 8:43 Martin Liska
2022-09-06 4:52 Martin Liska
2022-09-05 9:22 Martin Liska
2022-09-05 8:45 Martin Liska
2022-08-24 8:10 Martin Liska
2022-08-10 7:18 Martin Liska
2022-08-09 13:30 Martin Liska
2022-08-08 7:05 Martin Liska
2022-08-01 3:54 Martin Liska
2022-07-26 12:28 Martin Liska
2022-07-26 12:09 Martin Liska
2022-07-26 8:04 Martin Liska
2022-07-25 7:01 Martin Liska
2022-07-21 14:12 Martin Liska
2022-07-19 13:41 Martin Liska
2022-07-18 7:51 Martin Liska
2022-07-14 9:34 Martin Liska
2022-07-14 8:35 Martin Liska
2022-07-14 8:23 Martin Liska
2022-07-12 11:24 Martin Liska
2022-07-10 14:45 Martin Liska
2022-06-17 11:35 Martin Liska
2022-06-17 11:06 Martin Liska
2022-03-15 9:13 Martin Liska
2022-03-10 9:42 Martin Liska
2022-03-06 15:29 Martin Liska
2022-01-28 13:08 Martin Liska
2022-01-24 12:35 Martin Liska
2022-01-20 12:38 Martin Liska
2022-01-18 14:25 Martin Liska
2022-01-12 12:35 Martin Liska
2022-01-03 19:33 Martin Liska
2022-01-03 10:16 Martin Liska
2021-12-30 13:34 Martin Liska
2021-12-29 12:43 Martin Liska
2021-12-28 10:14 Martin Liska
2021-12-28 10:06 Martin Liska
2021-12-22 11:17 Martin Liska
2021-12-22 11:08 Martin Liska
2021-12-22 11:03 Martin Liska
2021-12-20 10:01 Martin Liska
2021-12-17 14:04 Martin Liska
2021-12-16 14:23 Martin Liska
2021-12-16 13:11 Martin Liska
2021-12-13 10:57 Martin Liska
2021-12-12 21:22 Martin Liska
2021-12-09 10:39 Martin Liska
2021-12-01 12:31 Martin Liska
2021-11-25 12:26 Martin Liska
2021-11-23 10:28 Martin Liska
2021-11-22 16:39 Martin Liska
2021-11-22 12:58 Martin Liska
2021-11-16 14:50 Martin Liska
2021-10-21 9:51 Martin Liska
2021-10-18 12:43 Martin Liska
2021-08-27 8:52 Martin Liska
2021-08-26 9:23 Martin Liska
2021-08-24 14:43 Martin Liska
2021-08-24 7:30 Martin Liska
2021-08-23 13:42 Martin Liska
2021-08-23 10:35 Martin Liska
2021-08-19 10:03 Martin Liska
2021-08-18 14:13 Martin Liska
2021-08-09 9:15 Martin Liska
2021-08-06 10:38 Martin Liska
2021-08-05 17:50 Martin Liska
2021-08-03 13:50 Martin Liska
2021-07-12 9:41 Martin Liska
2021-06-30 4:49 Martin Liska
2021-06-29 6:49 Martin Liska
2021-06-28 11:11 Martin Liska
2021-06-25 8:52 Martin Liska
2021-06-24 14:10 Martin Liska
2021-06-23 8:20 Martin Liska
2021-06-22 7:48 Martin Liska
2021-06-21 7:33 Martin Liska
2021-06-17 10:06 Martin Liska
2021-06-16 12:19 Martin Liska
2021-06-15 12:35 Martin Liska
2021-06-14 14:08 Martin Liska
2021-06-14 14:05 Martin Liska
2021-06-14 13:38 Martin Liska
2021-06-14 9:40 Martin Liska
2021-06-11 11:03 Martin Liska
2021-06-10 6:22 Martin Liska
2021-06-09 11:40 Martin Liska
2021-06-08 7:47 Martin Liska
2021-06-07 13:38 Martin Liska
2021-06-06 14:57 Martin Liska
2021-06-04 11:37 Martin Liska
2021-06-03 10:53 Martin Liska
2021-06-02 12:46 Martin Liska
2021-06-02 6:59 Martin Liska
2021-05-31 9:31 Martin Liska
2021-05-28 12:29 Martin Liska
2021-05-27 7:52 Martin Liska
2021-05-26 7:35 Martin Liska
2021-05-26 7:29 Martin Liska
2021-05-25 13:01 Martin Liska
2021-05-24 9:40 Martin Liska
2021-05-18 9:25 Martin Liska
2021-05-17 13:53 Martin Liska
2021-05-11 17:33 Martin Liska
2021-04-22 7:11 Martin Liska
2021-04-20 8:02 Martin Liska
2021-04-19 11:44 Martin Liska
2021-04-15 12:51 Martin Liska
2021-04-14 10:30 Martin Liska
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=20210810071242.36F583951C83@sourceware.org \
--to=marxin@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-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: 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).