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/marxin/heads/casm-refactoring-v1] (13 commits) asm_out_file renaming
Date: Wed, 15 Sep 2021 14:40:45 +0000 (GMT) [thread overview]
Message-ID: <20210915144045.3527C3858403@sourceware.org> (raw)
The branch 'marxin/heads/casm-refactoring-v1' was updated to point to:
533c540e42e... asm_out_file renaming
It previously pointed to:
c493b80e935... Rename in header files.
Diff:
!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------
c493b80... Rename in header files.
55ce188... Do not hide asm_out_file in ASM_OUTPUT_ASCII.
f042e05... Come up with casm global state.
Summary of changes (added commits):
-----------------------------------
533c540... asm_out_file renaming
4a5ef88... Do not hide asm_out_file in ASM_OUTPUT_ASCII.
c1328c1... Come up with casm global state.
a37d7d6... gcc-changelog: Add FIXME note. (*)
e0fcdc4... gcc-changelog: check git commit email address (*)
26d4ba0... target/102348 - fix powerpc-lynxos build (*)
7fc4d60... Optimize for V{8,16,32}HFmode vec_set/extract/init. (*)
feebc22... Maintain (mis-)alignment info in the first element of a gro (*)
e4d3643... AVX512FP16: Adjust builtin name for FP16 builtins to match (*)
b6d8fa6... tree-optimization/102318 - reduction epilogue re-use (*)
cc1e288... libstdc++: Check for TLS support on mingw cross-compilers (*)
243e0a5... Output vextract{i,f}{32x4,64x2} for (vec_select:(reg:Vmode) (*)
8b69c48... Add OpenACC 'host_data' testing to 'gfortran.dg/goacc/unexp (*)
(*) This commit already exists in another branch.
Because the reference `refs/users/marxin/heads/casm-refactoring-v1' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2021-09-15 14:40 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=20210915144045.3527C3858403@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).