public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	"Frédéric Pierret" <frederic.pierret@qubes-os.org>
Subject: [GIT PULL] gcc-plugins fixes for v5.7-rc5
Date: Mon, 4 May 2020 10:46:49 -0700	[thread overview]
Message-ID: <202005041045.BC2557B6@keescook> (raw)

Hi Linus,

Please pull these gcc-plugins fixes for v5.7-rc5. These are some more
clean-ups for using the plugins under GCC 10.

Thanks!

-Kees

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v5.7-rc5

for you to fetch changes up to c7527373fe28f97d8a196ab562db5589be0d34b9:

  gcc-common.h: Update for GCC 10 (2020-04-13 10:19:20 -0700)

----------------------------------------------------------------
GCC 10 fixes for gcc-plugins

- Adjust caller of cgraph_create_edge for GCC 10 argument usage
- Update common headers to build under GCC 10 (Frédéric Pierret)

----------------------------------------------------------------
Frédéric Pierret (fepitre) (1):
      gcc-common.h: Update for GCC 10

Kees Cook (1):
      gcc-plugins/stackleak: Avoid assignment for unused macro argument

 scripts/gcc-plugins/Makefile           | 1 +
 scripts/gcc-plugins/gcc-common.h       | 4 ++++
 scripts/gcc-plugins/stackleak_plugin.c | 5 ++---
 3 files changed, 7 insertions(+), 3 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2020-05-04 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 17:46 Kees Cook [this message]
2020-05-04 18:35 ` [GIT PULL] gcc-plugins fixes for v5.7-rc5 pr-tracker-bot

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=202005041045.BC2557B6@keescook \
    --to=keescook@chromium.org \
    --cc=frederic.pierret@qubes-os.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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