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] (8 commits) Merge branch 'master' into devel/sphinx
Date: Tue, 26 Jul 2022 12:09:25 +0000 (GMT)	[thread overview]
Message-ID: <20220726120925.53F1D385829E@sourceware.org> (raw)

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

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

It previously pointed to:

 8f694e3f186... Merge branch 'master' into devel/sphinx

Diff:

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

  d683a5b... Merge branch 'master' into devel/sphinx
  78017ea... docs: fix crossing declaration of @defmac and @hook. (*)
  2333b58... c++: ICE with erroneous template redeclaration [PR106311] (*)
  2615502... Handle non constant ranges in irange pretty printer. (*)
  67248ad... Improve ptr_derefs_may_alias_p for the case of &STRING_CST (*)
  c906efc... aarch64: Move vreinterpret definitions into the compiler (*)
  f023cc5... aarch64: Consolidate simd type lookup functions (*)
  8a1e05b... aarch64: Lower vcombine to GIMPLE (*)

(*) 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-26 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 12:09 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-10  7:18 Martin Liska
2021-12-13 10:57 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=20220726120925.53F1D385829E@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).