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] Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Mon, 21 Nov 2022 14:29:58 +0000 (GMT) [thread overview] Message-ID: <20221121142958.0F5B93853D40@sourceware.org> (raw) https://gcc.gnu.org/g:c0c5ff22c40a8f8e599959df400d3e613ba088be commit c0c5ff22c40a8f8e599959df400d3e613ba088be Merge: 20fe373390a a6b1f6126de Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Nov 21 15:27:57 2022 +0100 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Merge up to r12-8924-ga6b1f6126de5e45777610699b6d634605c17711c (21st Nov 2022) Diff: gcc/ChangeLog | 36 +++++++++++ gcc/DATESTAMP | 2 +- gcc/config/i386/avx512bf16intrin.h | 6 +- gcc/config/i386/avx512fp16intrin.h | 44 ++++++------- gcc/config/i386/avx512fp16vlintrin.h | 34 +++++----- gcc/config/i386/smmintrin.h | 13 ++-- gcc/config/loongarch/sync.md | 27 +++++++- gcc/config/nvptx/nvptx.h | 2 +- gcc/cp/ChangeLog | 22 +++++++ gcc/cp/cp-tree.h | 2 +- gcc/cp/semantics.cc | 2 +- gcc/cp/typeck.cc | 4 +- gcc/reg-stack.cc | 86 +++++++++++++++++++------ gcc/testsuite/ChangeLog | 25 +++++++ gcc/testsuite/gcc.dg/ubsan/pr107183.c | 12 ++++ gcc/testsuite/gcc.target/loongarch/pr107713-1.c | 50 ++++++++++++++ gcc/testsuite/gcc.target/loongarch/pr107713-2.c | 9 +++ libatomic/ChangeLog | 9 +++ libatomic/config/x86/init.c | 6 +- 19 files changed, 312 insertions(+), 79 deletions(-) diff --cc gcc/config/nvptx/nvptx.h index cfde6f191a4,294dd715c3d..b81f9f42cd3 --- a/gcc/config/nvptx/nvptx.h +++ b/gcc/config/nvptx/nvptx.h @@@ -27,15 -27,7 +27,15 @@@ /* Run-time Target. */ +/* Use '--with-arch' for default '-misa'. */ +#define OPTION_DEFAULT_SPECS \ + { "arch", "%{!misa=*:-misa=%(VALUE)}" }, \ + +/* Assembler supports '-v' option; handle similar to + '../../gcc.cc:asm_options', 'HAVE_GNU_AS'. */ +#define ASM_SPEC "%{v}" + - #define STARTFILE_SPEC "%{mmainkernel:crt0.o}" + #define STARTFILE_SPEC "%{mmainkernel:crt0.o%s}" #define TARGET_CPU_CPP_BUILTINS() nvptx_cpu_cpp_builtins ()
next reply other threads:[~2022-11-21 14:29 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-21 14:29 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-03-02 15:33 Tobias Burnus 2023-02-27 16:34 Tobias Burnus 2023-02-20 6:52 Tobias Burnus 2023-02-13 9:21 Tobias Burnus 2023-02-06 7:42 Tobias Burnus 2023-02-02 9:20 Tobias Burnus 2023-01-30 9:11 Tobias Burnus 2023-01-26 10:22 Tobias Burnus 2023-01-23 8:29 Tobias Burnus 2023-01-19 20:24 Tobias Burnus 2023-01-16 11:27 Tobias Burnus 2023-01-09 9:21 Tobias Burnus 2022-12-27 10:54 Tobias Burnus 2022-12-21 18:21 Tobias Burnus 2022-12-19 17:32 Tobias Burnus 2022-12-12 14:26 Tobias Burnus 2022-12-09 8:39 Tobias Burnus 2022-12-01 7:40 Tobias Burnus 2022-11-25 10:37 Tobias Burnus 2022-11-18 9:48 Tobias Burnus 2022-11-14 15:41 Tobias Burnus 2022-11-04 12:50 Tobias Burnus 2022-11-02 8:07 Tobias Burnus 2022-10-27 12:39 Tobias Burnus 2022-10-24 10:21 Tobias Burnus 2022-10-18 9:12 Tobias Burnus 2022-10-11 8:26 Tobias Burnus 2022-09-29 14:45 Tobias Burnus 2022-09-28 7:53 Tobias Burnus 2022-09-23 8:48 Tobias Burnus 2022-09-09 13:39 Tobias Burnus 2022-09-05 8:19 Tobias Burnus 2022-08-31 6:14 Tobias Burnus 2022-08-03 12:17 Tobias Burnus 2022-08-01 13:03 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-05 10:32 Tobias Burnus 2022-07-01 18:13 Kwok Yeung
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=20221121142958.0F5B93853D40@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).