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] (16 commits) Merge branch 'master' into devel/sphinx
Date: Mon,  7 Jun 2021 13:38:21 +0000 (GMT)	[thread overview]
Message-ID: <20210607133821.196FB3886C56@sourceware.org> (raw)

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

 6467a4e9a6c... Merge branch 'master' into devel/sphinx

It previously pointed to:

 7584ede9408... Remove license entry in intrinsic.

Diff:

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

  6467a4e... Merge branch 'master' into devel/sphinx
  4d3907c... Reformat target.def for better parsing. (*)
  3e00f8d... For obj-c stage-final re-use the checksum from the previous (*)
  e1521b1... fold-const: Fix up fold_read_from_vector [PR100887] (*)
  d66a703... tree-inline: Fix up __builtin_va_arg_pack handling [PR10089 (*)
  be5efe9... Fix ICE of insn does not satisfy its constraints. (*)
  9a90b31... Fix _mm256_zeroupper by representing the instructions as ca (*)
  16465ce... CALL_INSN may not be a real function call. (*)
  7d6987e... Daily bump. (*)
  fed94fc... Reimplement LEAF_REG_REMAP macro for the SPARC (*)
  03d921a... aix: Use assemble_name to output BSS section name. (*)
  09bf527... i386: Clean up constraints.md (*)
  cb4b99b... openmp: Add testcase for scan directive with nested functio (*)
  7fa4db3... openmp: Call c_omp_adjust_map_clauses even for combined tar (*)
  fcbbf78... docs: Add missing @headitem for tables. (*)
  0bc0e61... genhooks: remove dead code (*)

(*) 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:[~2021-06-07 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 13:38 Martin Liska [this message]
2022-07-26  8:04 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=20210607133821.196FB3886C56@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).