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] (5 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Thu, 29 Sep 2022 14:44:58 +0000 (GMT) [thread overview] Message-ID: <20220929144458.3EEA43858D39@sourceware.org> (raw) The branch 'devel/omp/gcc-12' was updated to point to: c455181c13a... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 It previously pointed to: d21bfef9867... OpenMP: Fix ICE with OMP metadirectives Diff: Summary of changes (added commits): ----------------------------------- c455181... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 85adc2e... libstdc++: Disable volatile-qualified std::bind for C++20 (*) afea1ae... OpenACC: Fix reduction tree-sharing issue [PR106982] (*) 7f323c2... Daily bump. (*) 6a59bac... aarch64: Add Arm Neoverse V2 support (*) (*) 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-09-29 14:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-29 14:44 Tobias Burnus [this message] 2023-03-02 15:32 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=20220929144458.3EEA43858D39@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).