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 r13-7687] Daily bump. Date: Sat, 5 Aug 2023 00:20:31 +0000 (GMT) [thread overview] Message-ID: <20230805002031.C41F63858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:e15cd6f0d8143e509d2d45f5bfa4d0445b7fff6b commit r13-7687-ge15cd6f0d8143e509d2d45f5bfa4d0445b7fff6b Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sat Aug 5 00:20:10 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 15 +++++++++++++++ gcc/DATESTAMP | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 84f998e8149..e8556ff32cc 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,18 @@ +2023-08-04 Georg-Johann Lay <avr@gjlay.de> + + * config/avr/avr-mcus.def (avr64dd14, avr64dd20, avr64dd28, avr64dd32) + (avr64ea28, avr64ea32, avr64ea48, attiny424, attiny426, attiny427) + (attiny824, attiny826, attiny827, attiny1624, attiny1626, attiny1627) + (attiny3224, attiny3226, attiny3227, avr16dd14, avr16dd20, avr16dd28) + (avr16dd32, avr32dd14, avr32dd20, avr32dd28, avr32dd32) + (attiny102, attiny104): New devices. + * doc/avr-mmcu.texi: Regenerate. + +2023-08-04 Georg-Johann Lay <avr@gjlay.de> + + * config/avr/avr-mcus.def (avr128d*, avr64d*): Fix their FLASH_SIZE + and PM_OFFSET entries. + 2023-08-01 Georg-Johann Lay <avr@gjlay.de> PR target/110220 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index f1bb943f0fd..2a6df2c1333 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230804 +20230805
reply other threads:[~2023-08-05 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=20230805002031.C41F63858D1E@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).