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: Mon, 18 Jul 2022 07:51:12 +0000 (GMT)	[thread overview]
Message-ID: <20220718075112.5058D3858C27@sourceware.org> (raw)

The branch 'devel/sphinx' was updated to point to:

 85df616e13a... Merge branch 'master' into devel/sphinx

It previously pointed to:

 c29d4ad6d7f... Merge branch 'master' into devel/sphinx

Diff:

Summary of changes (added commits):
-----------------------------------

  85df616... Merge branch 'master' into devel/sphinx
  2907bfc... PR target/106231: Optimize (any_extend:DI (ctz:SI ...)) on  (*)
  43c2505... Fix issue with x86_64_const_vector_operand predicate on x86 (*)
  f9da266... Add UNSPEC_MASKOP to kupck<mode> instructions in sse.md on  (*)
  6d70717... Daily bump. (*)
  7bcd7f4... Daily bump. (*)
  2b5baae... go: fix f().x where f returns zero-sized type (*)
  d6d8e6a... xtensa: Optimize "bitwise AND with imm1" followed by "branc (*)
  1884f89... xtensa: constantsynth: Make try to find shorter instruction (*)
  bdc7b76... Daily bump. (*)
  2582080... x86: Disable sibcall if indirect_return attribute doesn't m (*)
  fd3d25d... PR target/106273: Add earlyclobber to *andn<dwi>3_doublewor (*)
  517fb1a... Fortran: do not generate conflicting results under -ff2c [P (*)
  9a15d3b... c++: Add __reference_con{struc,ver}ts_from_temporary [PR104 (*)
  0a8edfb... analyzer: fix taint false positive on optimized range check (*)
  b1d07b5... analyzer: documentation nits relating to new fd warnings (*)
  5054bc0... go: fix f(g()) where g returns zero-sized type (*)
  91259dd... aarch64: Remove qualifier_internal (*)
  5ba864c... aarch64: Add V1DI mode (*)
  23dd41c... MAINTAINERS: Add myself to Write After Approval (*)
  2fd215b... PR target/106278: Keep REG_EQUAL notes consistent during TI (*)
  3aab916... Use pp_vrange for ranges in dump_ssaname_info. (*)
  64864aa... Convert vrange dumping facilities to pretty_printer. (*)
  91a7f30... Implement visitor pattern for vrange. (*)
  f858fe7... libcpp: Improve encapsulation of label_text (*)
  ae69e6f... i386: Fix _mm_[u]comixx_{ss,sd} codegen and add PF result.  (*)
  4cbebdd... [aarch64] Use op_mode instead of vmode in aarch64_vectorize (*)
  e0e07bc... Daily bump. (*)
  c6cf555... Simplify memchr with small constant strings (*)
  748f8a8... Fortran: error recovery for bad initializers of implied-sha (*)
  b4f8108... jit: Make recording::memento non-copyable (*)
  29f40a8... lto-plugin: use -pthread only for detected targets (*)
  b0f02ee... Fix ICE on view conversion between struct and integer (*)

(*) 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-18  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  7:51 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-20 10:01 Martin Liska
2021-06-17 10:06 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=20220718075112.5058D3858C27@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).