From: Gunther Nikl <gnikl@users.sourceforge.net>
To: Michael Meissner <meissner@linux.vnet.ibm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
segher@kernel.crashing.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #3
Date: Sat, 06 Oct 2012 19:47:00 -0000 [thread overview]
Message-ID: <50708AD5.2020205@users.sourceforge.net> (raw)
In-Reply-To: <20121005184737.GC29369@ibm-tiger.the-meissners.org>
Michael Meissner wrote:
> @@ -10326,7 +10352,7 @@ static rtx
> altivec_expand_ld_builtin (tree exp, rtx target, bool *expandedp)
> {
> tree fndecl = TREE_OPERAND (CALL_EXPR_FN (exp), 0);
> - unsigned int fcode = DECL_FUNCTION_CODE (fndecl);
> + enum rs6000_builtins fcode = (enum rs6000_builtins)
DECL_FUNCTION_CODE (fndecl);
> tree arg0;
> enum machine_mode tmode, mode0;
> rtx pat, op0;
There are several changes like that in your patch. Shouldn't these
changes be done in a separate patch?
Regards,
Gunther
next prev parent reply other threads:[~2012-10-06 19:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 22:44 [PATCH] Rs6000 infrastructure cleanup (switches) Michael Meissner
2012-09-15 16:49 ` Andreas Tobler
2012-09-17 17:04 ` Michael Meissner
2012-09-17 8:21 ` Iain Sandoe
2012-09-17 17:12 ` Michael Meissner
2012-09-17 19:52 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch Michael Meissner
2012-09-19 0:04 ` David Edelsohn
2012-09-19 20:00 ` Michael Meissner
2012-09-20 20:12 ` Michael Meissner
2012-09-27 22:57 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2b Michael Meissner
2012-09-28 19:24 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2c Michael Meissner
2012-10-01 23:11 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2d Michael Meissner
2012-10-02 17:44 ` David Edelsohn
2012-10-02 8:13 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2c Gunther Nikl
2012-10-02 16:12 ` Michael Meissner
2012-10-04 16:33 ` Gunther Nikl
2012-10-05 18:17 ` Michael Meissner
2012-10-05 18:48 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #3 Michael Meissner
2012-10-06 19:47 ` Gunther Nikl [this message]
2012-10-06 20:08 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2c Gunther Nikl
2012-10-04 1:42 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2b David Edelsohn
2012-10-05 18:31 ` Michael Meissner
2012-10-05 19:49 ` Michael Meissner
2012-10-09 23:01 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2c Michael Meissner
2012-10-10 1:17 ` David Edelsohn
2012-10-09 23:20 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2d Michael Meissner
2012-10-10 1:18 ` David Edelsohn
2012-10-09 23:37 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2e Michael Meissner
2012-10-10 1:32 ` David Edelsohn
2012-10-09 23:39 ` [PATCH] Rs6000 infrastructure cleanup (switches), question Michael Meissner
2012-10-10 16:56 ` David Edelsohn
2012-10-13 6:13 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #4 Michael Meissner
2012-10-15 15:58 ` Joseph S. Myers
2012-10-15 16:43 ` Michael Meissner
2012-10-16 15:10 ` Joseph S. Myers
2012-10-16 19:19 ` Michael Meissner
2012-10-16 22:50 ` [PATCH] TARGET_<xxx> support, was [PATCH] Rs6000 infrastructure cleanup Michael Meissner
2012-10-16 23:54 ` Richard Henderson
2012-10-17 9:55 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #4 Joseph S. Myers
2012-10-17 19:54 ` Michael Meissner
2012-10-16 16:13 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2f Michael Meissner
2012-10-17 19:42 ` David Edelsohn
2012-10-17 20:48 ` Michael Meissner
2012-10-18 15:46 ` Eric Botcazou
2012-09-27 22:56 ` [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2 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=50708AD5.2020205@users.sourceforge.net \
--to=gnikl@users.sourceforge.net \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
--cc=segher@kernel.crashing.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).