Well, at least with my cross it does.
this change, or something like it:
http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=09a77c2ea0b41fdff8820cbcbe41b35762db5c45
introduces a reference to TS_TYPED into the 4.6 branch for
fold-const.c, and it isnt defined,
or at least neither I nor my compiler c
On Mon, Feb 27, 2012 at 10:00 AM, Peter Garbett
wrote:
> Well, at least with my cross it does.
>
> this change, or something like it:
>
> http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=09a77c2ea0b41fdff8820cbcbe41b35762db5c45
>
> introduces a reference to TS_TYPED into the 4.6 branch for
> fold-
Thanks for the prompt and indeed helpful hint.
I'll comment the offending line out locally for now.
On Mon, Feb 27, 2012 at 9:08 AM, Richard Guenther
wrote:
> On Mon, Feb 27, 2012 at 10:00 AM, Peter Garbett
> wrote:
>> Well, at least with my cross it does.
>>
>> this change, or something like
On Mon, Feb 27, 2012 at 10:08 AM, Richard Guenther
wrote:
>> Well, at least with my cross it does.
>>
>> this change, or something like it:
>>
>> http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=09a77c2ea0b41fdff8820cbcbe41b35762db5c45
>>
>> introduces a reference to TS_TYPED into the 4.6 branch f
On Mon, Feb 27, 2012 at 10:28 AM, Uros Bizjak wrote:
> On Mon, Feb 27, 2012 at 10:08 AM, Richard Guenther
> wrote:
>>> Well, at least with my cross it does.
>>>
>>> this change, or something like it:
>>>
>>> http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=09a77c2ea0b41fdff8820cbcbe41b35762db5c45
On Mon, Feb 27, 2012 at 10:45 AM, Richard Guenther
wrote:
Well, at least with my cross it does.
this change, or something like it:
http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=09a77c2ea0b41fdff8820cbcbe41b35762db5c45
introduces a reference to TS_TYPED into t
On Mon, Feb 27, 2012 at 10:48:35AM +0100, Uros Bizjak wrote:
> OK, I will revert the patch immediatelly, under assumption that your
> mail grants RM approval for 4.6 branch.
Yes, the reversion is fine.
Jakub
Status
==
The trunk is still in regression and documentation fixes only state
(so-called stage4).
We have reached a point where it is sufficiently stable for a first
release candidate. If there appear no serious release blockers in
the next few days expect a release candidate this week. As
On Fri, 2012-02-24 at 16:07 +0800, Jiangning Liu wrote:
> Hi,
>
> For the small case below, there are some redundant PHI expression stmt
> generated, and finally cause back-end generates redundant copy instructions
> due to some reasons around IRA.
>
> int *l, *r, *g;
> void test_func(int n)
> {
The core development team is very pleased to announce the availability
of PPL 0.12, a new release of the Parma Polyhedra Library.
This release includes portability improvements, a few bug fixes, and
performance improvements for the MIP and PIP solvers. and PIP
solvers. Configurability has also
Sorry for being late to the party.
On Wed, Feb 15, 2012 at 9:55 AM, Ian Lance Taylor wrote:
> Ouch, I did not know that the EABI left this open. That seems like a
> bug, because it prevents code from being interoperable. This is
> precisely the kind of thing an ABI should address. Does anybody
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> William J. Schmidt
> Sent: Monday, February 27, 2012 11:32 PM
> To: Jiangning Liu
> Cc: gcc@gcc.gnu.org; wschm...@gcc.gnu.org
> Subject: Re: A question about redundant PHI expression stmt
>
>
Hello. A couple years ago I got really excited about the gcc "split stacks"
feature that was being developed, and I recently noticed that it is ready to
use now. I thereby have been spending the last few days trying it with one of
my side-projects (currently just a toy, but something I hope to h
13 matches
Mail list logo
