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: Tue, 28 Dec 2021 10:06:03 +0000 (GMT)	[thread overview]
Message-ID: <20211228100603.1E5993858427@sourceware.org> (raw)

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

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

It previously pointed to:

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

Diff:

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

  af45888... Merge branch 'master' into devel/sphinx
  a187edd... driver: Improve option diagnostics [PR103465] (*)
  786973c... docs: replace http:// with https:// (*)
  242783c... i386: Fix handling of SUBREGs in divv2sf3 [PR103842] (*)
  472568f... Fix tdpbf16ps testcase (*)
  d1e111d... Daily bump. (*)
  3430132... Fortran: fix use of static_assert() to conform to C11 (*)
  ea8b564... Improve atomic store implementation on hppa-linux. (*)
  916ec36... c++: Add testcase for SFINAE w/ p[N] and incomplete type [P (*)
  88cdcb5... c++: hard error w/ ptr+N and incomplete type [PR103700] (*)
  9407058... ix86: Don't use the 'm' constraint for x86_64_general_opera (*)
  e078de2... testsuite: Avoid unwanted vecorization [PR95046] (*)
  500d3f0... RISC-V: fixed testcase riscv/pr103302.c (*)
  ad6091d... Daily bump. (*)
  d874830... i386: Check AX input in any_mul_highpart peepholes (*)
  9525c26... Fortran: speed up decimal output of integers (*)
  10ae994... Daily bump. (*)
  4ae906e... Fortran: simplify library code for integer-to-decimal conve (*)
  ffb5418... Daily bump. (*)
  8f92139... i386: Add V2SFmode DIV insn pattern [PR95046, PR103797] (*)
  43dadcf... Darwin: Amend a comment to be more inclusive [NFC]. (*)
  19bf83a... Darwin: Update rules for handling alignment of globals. (*)
  8381075... Darwin: Check for that flag-reorder-and-partition. (*)
  9a4a29e... Darwin: Define OBJECT_FORMAT_MACHO. (*)
  7d01da8... Daily bump. (*)
  8f34344... smuldi3_highpart.c: Replace long with long long for -mx32 (*)
  ef26c15... x86: PR target/103773: Fix wrong-code with -Oz from pop to  (*)
  61e5369... i386: Enable intrinsics that convert float and bf16 data to (*)
  9ac0730... Fix typo in type verification. (*)
  1a7ce85... Combine vpcmpuw + zero_extend to vpcmpuw. (*)
  9f9bc0b... Daily bump. (*)
  ff0ad4b... Fortran: BOZ literal constants are not interoperable (*)
  5474092... Fortran: CASE selector expressions must be scalar (*)
  9c1ce17... arm: Declare MVE types internally via pragma (*)
  8c61cef... arm: Move arm_simd_info array declaration into header (*)
  2281735... Fortran: allow __float128 on targets where long double is n (*)

(*) 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-12-28 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 10:06 Martin Liska [this message]
2022-07-21 14:12 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=20211228100603.1E5993858427@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).