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] (9 commits) Merge branch 'master' into devel/sphinx
Date: Mon, 23 Aug 2021 13:42:33 +0000 (GMT)	[thread overview]
Message-ID: <20210823134233.368723858417@sourceware.org> (raw)

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

 041709a62f1... Merge branch 'master' into devel/sphinx

It previously pointed to:

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

Diff:

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

  041709a... Merge branch 'master' into devel/sphinx
  3eb377b... docs: Fix -mpic-data-is-text-relative option placement. (*)
  57a9e63... Fortran/OpenMP: Improve duplicate errors (*)
  d4de7e3... Fortran/OpenMP: strict modifier on grainsize/num_tasks (*)
  12dc8ab... Fix scalar costing issue introduced by PR84512 fix. (*)
  5378781... analyzer: Fix PR analyzer/102020 (*)
  e772159... Improved handling of division/modulus in bit CCP. (*)
  7e5f9ea... Simplify (truncate:QI (subreg:SI (reg:QI x))) to (reg:QI x) (*)
  1d24402... Fold sign of LSHIFT_EXPR to eliminate no-op conversions. (*)

(*) 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-08-23 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 13:42 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-20 15:24 Martin Liska
2021-06-14 13:38 Martin Liska
2021-06-02 12:46 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=20210823134233.368723858417@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).