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] (11 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Fri, 18 Nov 2022 09:48:11 +0000 (GMT) [thread overview] Message-ID: <20221118094811.1FEF9384F487@sourceware.org> (raw) The branch 'devel/omp/gcc-12' was updated to point to: 1e2e86107cf... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 It previously pointed to: b4acb91ca45... nvptx/mkoffload.cc: Fix "$nohost" check Diff: Summary of changes (added commits): ----------------------------------- 1e2e861... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 4388416... gcn: Add __builtin_gcn_kernarg_ptr 14faa5f... c++: constinit on pointer to function [PR104066] (*) 61537f7... Daily bump. (*) e9f0d97... aarch64: Add support for Ampere-1A (-mcpu=ampere1a) CPU (*) 985a896... SRA: Limit replacement creation for accesses propagated fro (*) bdcacfd... Daily bump. (*) 964af39... Daily bump. (*) 9c45321... libstdc++: Fix std::move_only_function for incomplete param (*) c6bd8fa... libstdc++: Fix wstring conversions in filesystem::path [PR9 (*) a088d93... libstdc++: Set active union member in constexpr std::string (*) (*) 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.
next reply other threads:[~2022-11-18 9:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-18 9:48 Tobias Burnus [this message] 2022-12-09 8:39 Tobias Burnus 2022-12-27 10:54 Tobias Burnus
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=20221118094811.1FEF9384F487@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).