public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [7/11] rtl optimizer changes
Date: Wed, 06 Jul 2011 18:25:00 -0000	[thread overview]
Message-ID: <4E14A5B0.6060106@redhat.com> (raw)
In-Reply-To: <4E0E0575.7000901@codesourcery.com>

On 07/01/2011 10:35 AM, Bernd Schmidt wrote:
> 	* explow.c (trunc_int_for_mode): Use GET_MODE_PRECISION
> 	instead of GET_MODE_BITSIZE where appropriate.
> 	* rtlanal.c (subreg_lsb_1, subreg_get_info, nonzero_bits1,
> 	num_sign_bit_copies1, canonicalize_condition, low_bitmask_len,
> 	init_num_sign_bit_copies_in_rep): Likewise.
> 	* cse.c (fold_rtx, cse_insn): Likewise.
> 	* loop-doloop.c (doloop_modify, doloop_optimize): Likewise.
> 	* simplify-rtx.c (simplify_unary_operation_1,
> 	simplify_const_unary_operation, simplify_binary_operation_1,
> 	simplify_const_binary_operation, simplify_ternary_operation,
> 	simplify_const_relational_operation, simplify_subreg): Likewise.
> 	* combine.c (try_combine, find_split_point, combine_simplify_rtx,
> 	simplify_if_then_else, simplify_set, expand_compound_operation,
> 	expand_field_assignment, make_extraction, if_then_else_cond,
> 	make_compound_operation, force_to_mode, make_field_assignment,
> 	reg_nonzero_bits_for_combine, reg_num_sign_bit_copies_for_combine,
> 	extended_count, try_widen_shift_mode, simplify_shift_const_1,
> 	simplify_comparison, record_promoted_value, simplify_compare_const,
> 	record_dead_and_set_regs_1): Likewise.

Ok.


r~

  reply	other threads:[~2011-07-06 18:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 17:26 [0/11] GET_MODE_PRECISION vs GET_MODE_BITSIZE Bernd Schmidt
2011-07-01 17:27 ` [1/11] Use targetm.shift_truncation_mask more consistently Bernd Schmidt
2011-07-04 15:29   ` Richard Henderson
2011-07-06 18:13   ` Richard Sandiford
2011-07-07  0:03     ` Bernd Schmidt
2011-07-07  8:07       ` Richard Sandiford
2011-07-01 17:30 ` [2/11] Neater tests for signbits Bernd Schmidt
2011-07-05 19:10   ` Richard Henderson
2011-07-05 21:35     ` Bernd Schmidt
2011-07-01 17:30 ` [3/11] Remove some dead code Bernd Schmidt
2011-07-05 19:12   ` Richard Henderson
2011-07-01 17:32 ` [4/11] Use precisions for TRULY_NOOP_TRUNCATION Bernd Schmidt
2011-07-05 19:16   ` Richard Henderson
2011-07-01 17:33 ` [5/11] Neater tests for paradoxical subregs Bernd Schmidt
2011-07-05 19:19   ` Richard Henderson
2011-07-01 17:34 ` [6/11] Tests for HOST_WIDE_INT representability Bernd Schmidt
2011-07-05 19:19   ` Richard Henderson
2011-07-01 17:36 ` [7/11] rtl optimizer changes Bernd Schmidt
2011-07-06 18:25   ` Richard Henderson [this message]
2011-07-01 17:37 ` [8/11] Expander changes Bernd Schmidt
2011-07-06 18:26   ` Richard Henderson
2011-07-01 17:38 ` [9/11] Fix units mismatch in comparison Bernd Schmidt
2011-07-06 18:27   ` Richard Henderson
2011-07-01 17:41 ` [10/11] Expander fixes for 40-bit integers Bernd Schmidt
2011-07-06 18:37   ` Richard Henderson
2011-07-01 17:42 ` [11/11] Fix get_mode_bounds Bernd Schmidt
2011-07-06 18:38   ` Richard Henderson
2011-07-06 23:16     ` Bernd Schmidt
2011-07-06 23:39       ` Richard Henderson
2011-07-11 10:38     ` Bernd Schmidt

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=4E14A5B0.6060106@redhat.com \
    --to=rth@redhat.com \
    --cc=bernds@codesourcery.com \
    --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).