Snapshot gcc-4.3-20080515 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20080515/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Hi,
> So the statement
> j_12 = D.1190_11 + j_24;
> is now present in loop_b, but I am unable to create the phi node for
> it in loop_b. I tried to do so using
> for (phi = phi_nodes (loop_a->header);
> phi;)
>{
> next = PHI_CHAIN (phi);
> create_phi_node (SSA_NAME_VAR (PHI_RES
> Ok, I'll take care of properly comitting the patch.
Thanks!
On Thu, May 15, 2008 at 8:15 PM, DJ Delorie <[EMAIL PROTECTED]> wrote:
>
>> The patch simply enabled type checking by default. As I don't see how
>> we can easily address the underlying problem can you try the following
>> which simply makes this typechecking weaker?
>
> That seems to work.
>
> FY
> The patch simply enabled type checking by default. As I don't see how
> we can easily address the underlying problem can you try the following
> which simply makes this typechecking weaker?
That seems to work.
FYI test results show 98% pass rate for C++ and 98.6% pass rate for C,
so I'm not s
chris kuhlman wrote:
> Hello:
>
> I wrote to the help gcc site and got no response, so I am writing here.
> Help would be immensely appreciated.
>
> I am trying to build GCC 4.3.0. I built GMP 4.2.2 and MPFR 2.3.1,
> and then I built GCC 4.3.0. Everything appeared to go fine. I
> installed co
-- Forwarded message --
From: Sandeep Maram <[EMAIL PROTECTED]>
Date: Thu, May 15, 2008 at 6:46 PM
Subject: Re: How to handle loop iterator variable?
To: Sebastian Pop <[EMAIL PROTECTED]>
Cc: gcc@gcc.gnu.org
> In lambda-code.c:1858 you have some code that does a similar renaming:
> In lambda-code.c:1858 you have some code that does a similar renaming:
>
> FOR_EACH_IMM_USE_STMT (stmt, imm_iter, oldiv_def)
> FOR_EACH_IMM_USE_ON_STMT (use_p, imm_iter)
>propagate_value (use_p, newiv);
>
>
The function replace_uses_by() also does the same renaming and it is
suitable in my c
On Thu, May 15, 2008 at 2:44 AM, DJ Delorie <[EMAIL PROTECTED]> wrote:
>
> More digging has identified this patch as the cause of the ongoing
> C++-related m32c build failures:
>
> 2008-03-24 Richard Guenther <[EMAIL PROTECTED]>
>
> PR c/22371
> * gimplify.c (gimplify_modify_ex
