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-10] (13 commits) [PATCH] OpenMP/Fortran: Fix (re)mapping of allocatable/poin Date: Tue, 15 Sep 2020 08:43:55 +0000 (GMT) [thread overview] Message-ID: <20200915084355.9AA023857801@sourceware.org> (raw) The branch 'devel/omp/gcc-10' was updated to point to: a93cc852103... [PATCH] OpenMP/Fortran: Fix (re)mapping of allocatable/poin It previously pointed to: fafbe5379f9... [libgomp, nvptx] Add __sync_compare_and_swap_16 Diff: Summary of changes (added commits): ----------------------------------- a93cc85... [PATCH] OpenMP/Fortran: Fix (re)mapping of allocatable/poin e524656... Merge remote-tracking branch 'origin/releases/gcc-10' into f73772d... Daily bump. (*) 0ea1b39... doc: fix spelling of -fprofile-reproducibility (*) 1c34981... bpf: use the expected instruction for NOPs (*) 1dbb919... tree-optimization/96522 - transfer of flow-sensitive info i (*) e93428a... tree-optimization/97043 - fix latent wrong-code with SLP ve (*) 7ad48f0... i386: Fix array index in expander (*) 1bcbc4d... Daily bump. (*) 23ee7de... Improve costs for DImode shifts of interger constants. (*) 1660e83... Daily bump. (*) 08a0f33... Add new shrpsi and shrpdi instruction variants to gcc/confi (*) 32ca9bb... Daily bump. (*) (*) This commit already exists in another branch. Because the reference `refs/heads/devel/omp/gcc-10' matches your hooks.email-new-commits-only configuration, no separate email is sent for this commit.
reply other threads:[~2020-09-15 8:43 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=20200915084355.9AA023857801@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).