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] (36 commits) Merge branch 'master' into devel/sphinx
Date: Thu, 21 Jul 2022 14:12:22 +0000 (GMT) [thread overview]
Message-ID: <20220721141222.137BA3853818@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
bb743388df9... Merge branch 'master' into devel/sphinx
It previously pointed to:
e9c8572e74d... Merge branch 'master' into devel/sphinx
Diff:
Summary of changes (added commits):
-----------------------------------
bb74338... Merge branch 'master' into devel/sphinx
24eae97... docs: remove trailing dots for 2 Fortran fns (*)
9a52d68... Revert "forwprop: Use lhs type instead of arg0 in folding V (*)
375668e... tree-optimization/106379 - add missing ~(a ^ b) folding for (*)
dc477ff... tree-optimization/106378 - DSE of LEN_STORE and MASK_STORE (*)
bd9837b... Teach VN about masked/len stores (*)
f4ed610... MAINTAINERS: Add myself as Ada front end co-maintainer (*)
6877993... Add alias disambiguation for vectorizer load/store IFNs (*)
742377e... analyzer: bulletproof taint warnings against NULL m_arg (*)
a6c192e... analyzer: fix ICE on untracked decl_regions [PR106374] (*)
e7dfd87... Daily bump. (*)
87a9bfe... libstdc++: Fix std::common_iterator triviality [PR100823] (*)
56c9998... libstdc++: Fix std::common_iterator assignment [PR100823] (*)
3b5567c... libstdc++: Fix minor bugs in std::common_iterator (*)
5e83069... analyzer: update "tainted" state of RHS in comparisons [PR1 (*)
26bbe78... Fortran: fix parsing of omp task affinity iterator clause [ (*)
daa36cf... Avoid registering __builtin_setjmp_receiver label twice [PR (*)
8694390... Remove unused remove_node_from_expr_list (*)
5f59d0f... Improve SLP codegen, avoiding unnecessary TREE_ADDRESSABLE (*)
78d5e12... Move pass_cse_sincos after vectorizer. (*)
f9d4c3b... Lower complex type move to enable vectorization for complex (*)
68871a0... analyzer: don't track string literals in the store [PR10635 (*)
7c0c10d... Daily bump. (*)
dbb093f... Resolve complicated join nodes in range_from_dom. (*)
b0cc57c... Remove recursion from range_from_dom. (*)
f838d15... Fortran: error recovery on invalid array reference of non-a (*)
c66dc02... libstdc++: Complete __gnu_debug::string Standard conformity (*)
68f3767... c++: shortcut bad reference binding [PR94894] (*)
7a158a5... tree-cfg: check placement of returns_twice calls (*)
26cea5f... tree-cfg: do not duplicate returns_twice calls (*)
76c3f0d... tree-ssa-sink: do not sink to in front of setjmp (*)
465802c... c++: Enable __has_builtin for new reference binding built-i (*)
4a8aab9... .gitignore: do not ignore config.h (*)
20ab397... libstdc++: Make __from_chars_alnum_to_val conversion explic (*)
2c044ff... analyzer: fix taint handling of switch statements [PR106321 (*)
434d521... analyzer: log out-edge description in exploded_graph::proce (*)
(*) 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:[~2022-07-21 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 14:12 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-28 10:06 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=20220721141222.137BA3853818@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: link
Be 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).