public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work164-test)] Update ChangeLog.* Date: Mon, 15 Apr 2024 22:38:42 +0000 (GMT) [thread overview] Message-ID: <20240415223842.DAB6D3858D35@sourceware.org> (raw) https://gcc.gnu.org/g:df331a2f871bed812082295bb7afaa3ddd81ea60 commit df331a2f871bed812082295bb7afaa3ddd81ea60 Author: Michael Meissner <meissner@linux.ibm.com> Date: Mon Apr 15 18:38:39 2024 -0400 Update ChangeLog.* Diff: --- gcc/ChangeLog.test | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/gcc/ChangeLog.test b/gcc/ChangeLog.test index fd5e9d14a39..146d70fca7f 100644 --- a/gcc/ChangeLog.test +++ b/gcc/ChangeLog.test @@ -1,3 +1,16 @@ +==================== Branch work164-test, patch #304 ==================== + +Adjust tests for tar register + +2024-04-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * gcc.target/powerpc/ppc-switch-1.c: Adjust test to account for using + the TAR regisgter. + * gcc.target/powerpc/safe-indirect-jump-3.c: Likewise. + * gcc.target/powerpc/safe-indirect-jump-3.c: Likewise. + ==================== Branch work164-test, patch #303 ==================== Update TAR support.
next reply other threads:[~2024-04-15 22:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-15 22:38 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-26 0:26 Michael Meissner 2024-04-25 22:12 Michael Meissner 2024-04-15 20:46 Michael Meissner 2024-04-13 2:48 Michael Meissner 2024-04-12 23:32 Michael Meissner 2024-04-12 23:08 Michael Meissner
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=20240415223842.DAB6D3858D35@sourceware.org \ --to=meissner@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).