public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-10264] Daily bump. Date: Tue, 20 Sep 2022 00:20:51 +0000 (GMT) [thread overview] Message-ID: <20220920002051.9E88D3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:e4824c66e4b0f6e2a5795f782c4c164563b293fd commit r11-10264-ge4824c66e4b0f6e2a5795f782c4c164563b293fd Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Sep 20 00:20:16 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- libgcc/config/avr/libf7/ChangeLog | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 98dc1b51fa6..54f97aaa2e6 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220919 +20220920 diff --git a/libgcc/config/avr/libf7/ChangeLog b/libgcc/config/avr/libf7/ChangeLog index 7e06f52d415..9081ecd3bd1 100644 --- a/libgcc/config/avr/libf7/ChangeLog +++ b/libgcc/config/avr/libf7/ChangeLog @@ -1,3 +1,12 @@ +2022-09-19 Georg-Johann Lay <avr@gjlay.de> + + Backported from master: + 2022-09-19 Georg-Johann Lay <avr@gjlay.de> + + PR target/99184 + * libf7-asm.sx (to_integer, to_unsigned): Don't round 16-bit + and 32-bit integers. + 2022-04-21 Release Manager * GCC 11.3.0 released.
reply other threads:[~2022-09-20 0:20 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=20220920002051.9E88D3858D28@sourceware.org \ --to=gccadmin@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: linkBe 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).