Quoting Kenneth Zadeck :
if (TREE_CODE (inner) == RSHIFT_EXPR
&& TREE_CODE (TREE_OPERAND (inner, 1)) == INTEGER_CST
&& TREE_INT_CST_HIGH (TREE_OPERAND (inner, 1)) == 0
&& bitnum < TYPE_PRECISION (type)
&& 0 > compare_tree_int (TREE_OPERAND (inner, 1),
On 07/01/2013 02:05 AM, Joel Sherrill wrote:
Have you compared it to -Os? That seems to produce assembly closer to
what you would likely write by hand. I haven't benchmarked it much but it
gives 7-10% smaller code in general. In many cases, fewer instructions is
also a performance win.
Hi Joel
Hi,
Near the start of schedule_block, find_modifiable_mems is called if
DONT_BREAK_DEPENDENCIES is not enabled for this scheduling pass. It seems on
c6x backend currently uses this.
However, it's quite strange that this is not a requirement for all backends
since find_modifiable_mems, moves all
On Thu, 2013-06-27 at 20:23 +, Joseph S. Myers wrote:
> On Thu, 27 Jun 2013, David Malcolm wrote:
>
> > I want to focus on "removal of global state", and I want that to be
> > separate from "cleanups of internal APIs".
There are several interpretations of the word "global" in this
conversatio
On Mon, 1 Jul 2013, David Malcolm wrote:
> > As for accessing globals directly versus via APIs: yes, I suppose you do
> > still have an access to a global class instance in each place you formerly
> > had a global variable (that's now a member of that class), so by itself
> > such a conversion
I started to do this starting with the C++ parser class'izing it but
no one was interested.
On 1 July 2013 20:43, Joseph S. Myers wrote:
> On Mon, 1 Jul 2013, David Malcolm wrote:
>
>> > As for accessing globals directly versus via APIs: yes, I suppose you do
>> > still have an access to a global
