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] (12 commits) Align with: "OpenMP/Fortran: 'target update' with DT compon Date: Fri, 4 Nov 2022 12:50:20 +0000 (GMT) [thread overview] Message-ID: <20221104125021.B39C4385843F@sourceware.org> (raw) The branch 'devel/omp/gcc-12' was updated to point to: f9d5362918e... Align with: "OpenMP/Fortran: 'target update' with DT compon It previously pointed to: f8a1c619be1... Fortran "declare create"/allocate support for OpenACC: adju Diff: Summary of changes (added commits): ----------------------------------- f9d5362... Align with: "OpenMP/Fortran: 'target update' with DT compon ac48362... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 14a9222... Daily bump. (*) 35e8b88... i386: Fix uninitialized register after peephole2 conversion (*) 31f25cf... c, c++: Fix up excess precision handling of scalar_to_vecto (*) 20ef7d7... c++: Fix up constexpr handling of char/signed char/short pr (*) 07a3101... libgomp: Fix up creation of artificial teams (*) 7d5e6cd... tree-cfg: Fix a verification diagnostic typo [PR107121] (*) c8dc6b0... openmp: Fix ICE with taskgroup at -O0 -fexceptions [PR10700 (*) a46f71c... openmp, c: Tighten up c_tree_equal [PR106981] (*) f755e36... openmp: Fix handling of target constructs in static member (*) f170f1e... Daily bump. (*) (*) This commit already exists in another branch. Because the reference `refs/heads/devel/omp/gcc-12' matches your hooks.email-new-commits-only configuration, no separate email is sent for this commit.
reply other threads:[~2022-11-04 12:50 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=20221104125021.B39C4385843F@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).