public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/aoliva/heads/testme] (23 commits) silence warnings
Date: Thu,  8 Jun 2023 09:16:40 +0000 (GMT)	[thread overview]
Message-ID: <20230608091640.BFD513858C62@sourceware.org> (raw)

The branch 'aoliva/heads/testme' was updated to point to:

 94f4fed8c01... silence warnings

It previously pointed to:

 b04c0f8657b... silence warnings

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  b04c0f8... silence warnings
  c33ae46... enable strub for all viable functions by default, for testi
  397d45c... [strub] tolerate call_stmt-less cgraph_edges
  37f768c... strub: introduce downward scrubbing
  36703cc... Adjust gnat.dg testsuite after fix for V509-015.
  2d689af... Introduce strub: machine-independent stack scrubbing
  6917e5c... Introduce hardbool attribute for C
  c281c09... enable control flow redundancy hardening unconditionally
  44e4b01... Add leafy mode for zero-call-used-regs [ada doc]
  26fcd52... hardcfr: optionally disable in leaf functions [ada doc]
  b1ea86d... hardcfr: optionally disable in leaf functions
  a273f6e... hardcfr: prevent deferred sets of visited bitmap
  ae6a9e6... Expose expected_throw attribute
  162a958... Expose expected_throw attribute
  532f9dc... Expose expected_throw attribute (Ada)
  17a068a... hardcfr: mark expected-throw functions
  38ed604... hardcfr: mark throw-expected functions [ada/gcc-interface]
  f71bfe6... hardcfr: mark throw-expected functions [ada doc]
  5667c51... hardcfr: add optional checkpoints [ada docs]
  6c914d0... hardcfr: add optional checkpoints
  5c648ed... Control flow redundancy hardening
  d707886... Add leafy mode for zero-call-used-regs


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

  94f4fed... silence warnings
  37750ab... enable strub for all viable functions by default, for testi
  ee0b724... [strub] tolerate call_stmt-less cgraph_edges
  26e7ad9... strub: introduce downward scrubbing
  f98ade3... Adjust gnat.dg testsuite after fix for V509-015.
  4f1705e... Introduce strub: machine-independent stack scrubbing
  b96122a... Add leafy mode for zero-call-used-regs [ada doc]
  ede7847... Add leafy mode for zero-call-used-regs
  1bfbbba... Introduce hardbool attribute for C
  b9c018b... enable control flow redundancy hardening unconditionally
  4e561e9... detect infinite loops earlier in returning_call_p
  c4d4a9f... hardcfr: optionally disable in leaf functions [ada doc]
  3334b47... hardcfr: optionally disable in leaf functions
  f505756... hardcfr: prevent deferred sets of visited bitmap
  2b92db9... Expose expected_throw attribute
  766368d... Expose expected_throw attribute
  b166a79... Expose expected_throw attribute (Ada)
  b5d67b1... hardcfr: mark expected-throw functions
  2cbdae3... hardcfr: mark throw-expected functions [ada/gcc-interface]
  e705568... hardcfr: mark throw-expected functions [ada doc]
  440aa02... hardcfr: add optional checkpoints [ada docs]
  f2bb0e3... hardcfr: add optional checkpoints
  76f3003... Control flow redundancy hardening

                 reply	other threads:[~2023-06-08  9:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230608091640.BFD513858C62@sourceware.org \
    --to=aoliva@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).