Hi,
I am investigating a bug in our target port. It is
due to following optimization done by combine pass.
(zero_extend:SI (reg:BI 120))
is transformed to
(and:SI (subreg:SI (reg:BI 120) 0)
(const_int 255 [0xff]))
in expand_compound_operation (combine.c), where BImode is
just treated as
Hello,
given that the has been quite some libquadmath-related configure work:
Are there still build problems due to link tests if one cross-builds for
bare-iron targets? Or not? (Cf. PR 46520)
If so, I would start to tackle them next.
(As work around, one can now use --disable-libquadmath; h
On Thu, Dec 9, 2010 at 8:55 PM, H.J. Lu wrote:
> On Thu, Dec 9, 2010 at 6:29 PM, H.J. Lu wrote:
>> On Wed, Dec 8, 2010 at 9:36 AM, H.J. Lu wrote:
>>> On Wed, Dec 8, 2010 at 5:54 AM, H.J. Lu wrote:
On Wed, Dec 8, 2010 at 1:19 AM, Andi Kleen wrote:
>> On 12/07/2010 04:20 PM, Andi Kleen
Hi,
I am kooking ways to reduce the code size. What loop optimizations could
increase the code size significantly?
The optimization I know are: unswitch, vectorization, prefetch and unrolling.
We should not perform these optimizations if the loop just roll a few
iterations.
In addition, what l
On Wed, 2010-12-08 at 14:42 +0100, Richard Guenther wrote:
> A release candidate for GCC 4.5.2 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.5.2-RC-20101208
>
> and shortly its mirrors. It has been generated from SVN revision 167585.
>
> I have so far bootstrapped and tested the
Hi lists,
I found a couple of new FAILs in my latest libjava testrun:
> FAIL: newarray_overflow -O3 compilation from source
> FAIL: newarray_overflow -O3 -findirect-dispatch compilation from source
These turn out to be tree checking failures:
> In file included from :3:0:
> newarray_ov
Software pipeline (a.k.a, sms) generates prologue and epilogue code.
In addition, loop versioning duplicates loop body, which would also
increase code size. But I guess you don't want to turn on SWP, right?
Gan
On Fri, Dec 10, 2010 at 1:40 PM, Fang, Changpeng wrote:
> Hi,
>
> I am kooking ways
On Fri, Dec 10, 2010 at 7:13 AM, H.J. Lu wrote:
> On Thu, Dec 9, 2010 at 8:55 PM, H.J. Lu wrote:
>> On Thu, Dec 9, 2010 at 6:29 PM, H.J. Lu wrote:
>>> On Wed, Dec 8, 2010 at 9:36 AM, H.J. Lu wrote:
On Wed, Dec 8, 2010 at 5:54 AM, H.J. Lu wrote:
> On Wed, Dec 8, 2010 at 1:19 AM, Andi K
On Fri, Dec 10, 2010 at 4:39 PM, H.J. Lu wrote:
> On Fri, Dec 10, 2010 at 7:13 AM, H.J. Lu wrote:
>> On Thu, Dec 9, 2010 at 8:55 PM, H.J. Lu wrote:
>>> On Thu, Dec 9, 2010 at 6:29 PM, H.J. Lu wrote:
On Wed, Dec 8, 2010 at 9:36 AM, H.J. Lu wrote:
> On Wed, Dec 8, 2010 at 5:54 AM, H.J.