public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/sphinx] (33 commits) Merge branch 'master' into devel/sphinx Date: Thu, 17 Jun 2021 10:06:10 +0000 (GMT) [thread overview] Message-ID: <20210617100610.DF4DB384402B@sourceware.org> (raw) The branch 'devel/sphinx' was updated to point to: d79a408d0e2... Merge branch 'master' into devel/sphinx It previously pointed to: 78a55ff9ef0... Merge branch 'master' into devel/sphinx Diff: Summary of changes (added commits): ----------------------------------- d79a408... Merge branch 'master' into devel/sphinx 8eac92a... docs: Use -O1 as a canonical value for -O option (*) c095405... gcov: update documentation entry about string format (*) a4fc63e... IBM Z: Fix vector intrinsics vec_double and vec_floate (*) 53c55d3... return auto_vec from more dominance functions (*) 4541b5e... make get_domminated_by_region return a auto_vec (*) 4f899c4... return auto_vec from get_dominated_by (*) a165040... return auto_vec from get_loop_hot_path (*) 265af87... return auto_vec from cgraph_node::collect_callers (*) e9681f5... auto_vec copy/move improvements (*) 3f3ee13... Add debugging helpers for ranger. (*) 3dfa4fe... Vectorization of BB reductions (*) 9f12bd7... Add amacleod and aldyh as *vrp and ranger maintainers. (*) 6075074... [Ada] Use runtime from base compiler during stage1 (continu (*) ff4deb4... c++: Tweak PR101029 fix (*) 9a61dfd... Daily bump. (*) 786188e... Add recomputation to outgoing_edge_range. (*) 8a22a10... Range_on_edge in ranger_cache should return true for all ra (*) 487be92... Correct documented option defaults. (*) 6816a44... c++: static memfn from non-dependent base [PR101078] (*) cfe0a2e... Fortran - ICE in gfc_check_do_variable, at fortran/parse.c: (*) d117f99... Revert "Fortran - ICE in gfc_check_do_variable, at fortran/ (*) 72e3d92... Fortran - ICE in gfc_check_do_variable, at fortran/parse.c: (*) bdfc120... Avoid loading an undefined value in the ranger_cache constr (*) 9e64426... libcpp: location comparison within macro [PR100796] (*) dd835ec... ii386: Add missing two element 64bit vector permutations [P (*) c25e3bf... libstdc++: Use named struct for __decay_copy (*) b9e35ee... libstdc++: Revert final/non-addressable changes to ranges C (*) dbfc149... aarch64: Model zero-high-half semantics of ADDHN/SUBHN inst (*) d0889b5... aarch64: Model zero-high-half semantics of [SU]QXTN instruc (*) c86a303... aarch64: Model zero-high-half semantics of SQXTUN instructi (*) d8a88cd... aarch64: Model zero-high-half semantics of XTN instruction (*) ac6c858... testsuite: aarch64: Add zero-high-half tests for narrowing (*) (*) This commit already exists in another branch. Because the reference `refs/heads/devel/sphinx' matches your hooks.email-new-commits-only configuration, no separate email is sent for this commit.
next reply other threads:[~2021-06-17 10:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-17 10:06 Martin Liska [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-07-18 7:51 Martin Liska 2021-12-20 10:01 Martin Liska 2021-05-18 9:25 Martin Liska
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=20210617100610.DF4DB384402B@sourceware.org \ --to=marxin@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).