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 r11-9739] LTO: bump bytecode version
Date: Wed, 30 Mar 2022 08:04:27 +0000 (GMT)	[thread overview]
Message-ID: <20220330080427.EF71C385DC1F@sourceware.org> (raw)

https://gcc.gnu.org/g:71aa6e9c36c6948a4de67720a0e9f368ce696f4e

commit r11-9739-g71aa6e9c36c6948a4de67720a0e9f368ce696f4e
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Mar 30 10:02:59 2022 +0200

    LTO: bump bytecode version
    
    The following revision 91f7d7e1bb6827bf8e0b7ba7eb949953a5b1bd18
    breaks bytecode as it introduces a new param.
    
    gcc/ChangeLog:
    
            * lto-streamer.h (LTO_minor_version): Bump it.

Diff:
---
 gcc/lto-streamer.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/lto-streamer.h b/gcc/lto-streamer.h
index e2a0e033ab2..db17b764957 100644
--- a/gcc/lto-streamer.h
+++ b/gcc/lto-streamer.h
@@ -121,7 +121,7 @@ along with GCC; see the file COPYING3.  If not see
      form followed by the data for the string.  */
 
 #define LTO_major_version 11
-#define LTO_minor_version 2
+#define LTO_minor_version 3
 
 typedef unsigned char	lto_decl_flags_t;


                 reply	other threads:[~2022-03-30  8:04 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=20220330080427.EF71C385DC1F@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).