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] (2 commits) Reject unaligned subregs when strict alignment is required Date: Thu, 5 May 2022 06:31:44 +0000 (GMT) [thread overview] Message-ID: <20220505063144.D7A3F3857349@sourceware.org> (raw) The branch 'aoliva/heads/testme' was updated to point to: b119a409842... Reject unaligned subregs when strict alignment is required It previously pointed to: 3d8a853f35a... Reject unaligned subregs when strict alignment is required Diff: !!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST): ------------------------------------------------------------------- 3d8a853... Reject unaligned subregs when strict alignment is required 3a9edb9... libstdc++: testsuite: async.cc early timeout Summary of changes (added commits): ----------------------------------- b119a40... Reject unaligned subregs when strict alignment is required 2c659d7... libstdc++: testsuite: async.cc early timeout
reply other threads:[~2022-05-05 6:31 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=20220505063144.D7A3F3857349@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: 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).