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] (8 commits) fix strub function type sharing
Date: Wed, 17 Nov 2021 05:16:19 +0000 (GMT)	[thread overview]
Message-ID: <20211117051619.3A9083858410@sourceware.org> (raw)

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

 8274a332110... fix strub function type sharing

It previously pointed to:

 3d5dbbfc928... reduce optimizations of functions called with overridden fn

Diff:

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

  3d5dbbf... reduce optimizations of functions called with overridden fn


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

  8274a33... fix strub function type sharing (*)
  0db4fa2... Remap at-calls calls with converted types (*)
  e8ec0b2... Improve integration of strub with type systems (*)
  9842c2c... Improve integration of strub with type systems (*)
  07866c7... improve integration of strub with type systems (*)
  e3c4210... introduce stack scrub (strub) feature (*)
  e40efa6... Revert "[Ada] introduce stack scrub (strub) feature" (*)
  4920c65... Revert "[Ada] Improve integration of strub with type system (*)

(*) This commit already exists in another branch.
    Because the reference `refs/users/aoliva/heads/testme' matches
    your hooks.email-new-commits-only configuration,
    no separate email is sent for this commit.


                 reply	other threads:[~2021-11-17  5: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=20211117051619.3A9083858410@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).