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] (13 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Mon, 16 Jan 2023 11:27:25 +0000 (GMT) [thread overview] Message-ID: <20230116112725.BC6843858D32@sourceware.org> (raw) The branch 'devel/omp/gcc-12' was updated to point to: d7995cf373a... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 It previously pointed to: c9b47ccf32a... libgomp, amdgcn: Switch USM to 128-byte alignment Diff: Summary of changes (added commits): ----------------------------------- d7995cf... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 d369eb4... Daily bump. (*) e172ba9... Daily bump. (*) f23ad9c... Daily bump. (*) 4c416a4... Daily bump. (*) c142b30... Daily bump. (*) eec3a65... Fix problematic interaction between bitfields, unions, SSO (*) bd4c310... strlen: do not use cond_expr for boundaries (*) 14e2500... Daily bump. (*) 25edc76... Fix memory constraint on MVE v[ld/st][2/4] instructions [PR (*) 849c3cf... aarch64: PR target/108140 Handle NULL target in data intrin (*) 56314aa... Daily bump. (*) 05fce80... Update cpplib eo.po (*) (*) 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:[~2023-01-16 11:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 11:27 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-02-06 7:42 Tobias Burnus 2022-12-21 18:21 Tobias Burnus 2022-09-05 8:18 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=20230116112725.BC6843858D32@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).