From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [RFC 0/3] Remove unused operators OP_BITSTRING TERNOP_SLICE_COUNT and TYPE_CODE_BITSTRING
Date: Fri, 10 Aug 2012 09:13:00 -0000 [thread overview]
Message-ID: <1344589936-2006-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
This patch set is a follow-up to my prosal here,
Remove OP_LABELED TERNOP_SLICE_COUNT and OP_BITSTRING?
http://sourceware.org/ml/gdb/2012-08/msg00018.html
However, OP_LABELED is not removed in this patch set, because it is not
obviously correct to do so, and more thoughts are needed. Removal of
TYPE_CODE_BITSTRING is added in this set.
I don't put much words in each patch, because each of them just simply
removes unused bits. Regression tested on x86_64-unknow-linux.
next reply other threads:[~2012-08-10 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 9:13 Yao Qi [this message]
2012-08-10 9:13 ` [PATCH 2/3] Remove TERNOP_SLICE_COUNT Yao Qi
2012-08-10 16:16 ` Tom Tromey
2012-08-10 9:13 ` [PATCH 3/3] remove TYPE_CODE_BITSTRING Yao Qi
2012-08-10 16:19 ` Tom Tromey
2012-08-13 1:13 ` Yao Qi
2012-08-15 19:39 ` Tom Tromey
2012-08-10 9:13 ` [PATCH 1/3] Remove OP_BITSTRING Yao Qi
2012-08-10 16:16 ` Tom Tromey
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=1344589936-2006-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.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