This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix PR49876: Continue code generation with integer_zero_node on gloog_error

From: Sebastian Pop <sebpop at gmail dot com>
To: Richard Guenther <rguenther at suse dot de>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, gcc-patches at gcc dot gnu dot org
Date: Thu, 28 Jul 2011 10:18:52 -0500
Subject: Re: [PATCH] Fix PR49876: Continue code generation with integer_zero_node on gloog_error
References: <1311792579-26332-1-git-send-email-sebpop@gmail.com> <CAFiYyc1uFWueavP3zD3bf0ntD10Nbf0hXcsm52x7obCUNjj6yw@mail.gmail.com> <CAFk3UF-9uaUALJzH770NeMh53P6sJpzZCJW67rfKW2VnU+f=ow@mail.gmail.com> <alpine.LNX.2.00.1107281648260.810@zhemvz.fhfr.qr>

On Thu, Jul 28, 2011 at 09:49, Richard Guenther <rguenther@suse.de> wrote:
> And it's always integers or pointers only? ?Otherwise you'd probably
> want build_zero_cst (type) instead.

Ok, I started regstrapping again with build_zero_cst.

Thanks,
Sebastian

References:
- [PATCH] Fix PR49876: Continue code generation with integer_zero_node on gloog_error
  - From: Sebastian Pop
- Re: [PATCH] Fix PR49876: Continue code generation with integer_zero_node on gloog_error
  - From: Richard Guenther
- Re: [PATCH] Fix PR49876: Continue code generation with integer_zero_node on gloog_error
  - From: Sebastian Pop

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]