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] (40 commits) Merge branch 'master' into devel/sphinx Date: Mon, 25 Jul 2022 07:01:13 +0000 (GMT) [thread overview] Message-ID: <20220725070113.5DE603858403@sourceware.org> (raw) The branch 'devel/sphinx' was updated to point to: 9630093982a... Merge branch 'master' into devel/sphinx It previously pointed to: bb743388df9... Merge branch 'master' into devel/sphinx Diff: Summary of changes (added commits): ----------------------------------- 9630093... Merge branch 'master' into devel/sphinx 718cf8d... docs: remove recently added trailing whitespaces (*) 1a10bd8... frange class to represent floating point ranges (*) 75d20d6... rs6000: Adjust -mdejagnu-cpu to filter out -mtune [PR106345 (*) 45f6ced... c++: correct testcase PR number (*) 6078e01... Daily bump. (*) 8b8103d... Minor fixes to vr_values to not die on non integral types. (*) 164758b... Tweaks to global ranges. (*) 4a36b4e... Allow registering same SSA name relations in oracle. (*) e850c98... Convert some uses in ranger_cache and DOM to vrange. (*) 76d6224... PR target/106303: Fix TImode STV related failures on x86. (*) 0e6fa99... Daily bump. (*) f8e6e2c... Adding three new function attributes for static analysis of (*) b563a8d... Daily bump. (*) 6d5194a... analyzer: fix state explosion on va_arg [PR106413] (*) 0fb35a4... analyzer: fix ICE in binding_cluster ctor [PR106401] (*) f77bbc8... c++: CTAD from initializer list [PR106366] (*) b585af3... c++: correct ChangeLog PR number (*) 27d2c49... Fix CL entry (*) b4cc945... Fix handling of zero capacity regions in -Wanalyzer-allocat (*) 64cb87b... xtensa: Optimize "bitwise AND NOT with imm" followed by "br (*) cf17256... libgo: use POSIX shell arithmetic expansion (*) 41da407... graphds: Fix description of SCC algorithm (*) 18ef76d... Allow space in git commit-mklog args (*) 786e516... libsanitizer: Fix Solaris 11.3 compilation [PR105531] (*) 03c0b06... mklog: fill-up subject prefix only for a single PR (*) d85e5ae... tree-optimization/106403 - fix ICE with VN of .STORE_LANES (*) b2e99bb... tree-optimization/106397 - array prefetch and LC SSA (*) 3c4af0f... tree-optimization/106387 - properly create SSA name for rea (*) aaf9583... remove 'continue' as last statement in loop (*) 1cc0e9a... Adjust testcase. (*) 605b642... Extend 16/32-bit vector bit_op patterns with (m,0,i) altern (*) 45e0683... [PATCH, rs6000] Cleanup some vstrir define_expand naming in (*) 75841b0... [PATCH, rs6000] Additional cleanup of rs6000_builtin_mask (*) bbb9c03... Daily bump. (*) b852aa7... analyzer: fix -Wanalyzer-va-list-exhausted false +ve on va_ (*) 633e992... match.pd: Add new abs pattern [PR94920] (*) 28be481... c++: defaulted friend op== [PR106361] (*) df118d7... c++: defaulted ctor with DMI in union [PR94823] (*) 142e6af... MAINTAINERS: Add myself to Write After Approval (*) (*) 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.
reply other threads:[~2022-07-25 7:01 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=20220725070113.5DE603858403@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).