From: tbsaunde+gcc@tbsaunde.org
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/7] More ifdef reduction
Date: Sat, 23 May 2015 22:45:00 -0000 [thread overview]
Message-ID: <1432421110-22114-1-git-send-email-tbsaunde+gcc@tbsaunde.org> (raw)
From: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
Hi,
yet more of the same.
each individually bootstrapped + regtested on x86_64-linux-gnu, and made sure
config-list.mk was fine at the end. I expect this stuff is all still
preapproved so committing to trunk.
Trev
Trevor Saunders (7):
always define HAVE_lo_sum
provide default for HAVE_mem_thread_fence
always define HAVE_memory_barrier
provide default for HAVE_mem_signal_fence
add default for HAVE_load_multiple
add default for HAVE_store_multiple
add default for HAVE_tablejump
gcc/ChangeLog | 46 ++++++++++++++++++++++++++++++++
gcc/combine.c | 10 +++----
gcc/config/darwin.c | 3 +--
gcc/defaults.h | 60 ++++++++++++++++++++++++++++++++++++++++++
gcc/expr.c | 11 --------
gcc/genconfig.c | 2 ++
gcc/lra-constraints.c | 72 +++++++++++++++++++++++++--------------------------
gcc/optabs.c | 14 ----------
gcc/stmt.c | 4 ---
9 files changed, 148 insertions(+), 74 deletions(-)
--
2.4.0.78.g7c6ecbf
next reply other threads:[~2015-05-23 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 22:45 tbsaunde+gcc [this message]
2015-05-23 22:45 ` [PATCH 1/7] always define HAVE_lo_sum tbsaunde+gcc
2015-05-23 22:45 ` [PATCH 6/7] add default for HAVE_store_multiple tbsaunde+gcc
2015-05-23 22:45 ` [PATCH 2/7] provide default for HAVE_mem_thread_fence tbsaunde+gcc
2015-05-23 22:45 ` [PATCH 3/7] always define HAVE_memory_barrier tbsaunde+gcc
2015-05-24 4:24 ` [PATCH 5/7] add default for HAVE_load_multiple tbsaunde+gcc
2015-05-24 5:05 ` [PATCH 7/7] add default for HAVE_tablejump tbsaunde+gcc
2015-05-24 6:47 ` [PATCH 4/7] provide default for HAVE_mem_signal_fence tbsaunde+gcc
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=1432421110-22114-1-git-send-email-tbsaunde+gcc@tbsaunde.org \
--to=tbsaunde+gcc@tbsaunde.org \
--cc=gcc-patches@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).