On Thu, 30 Oct 2014, David Edelsohn wrote:
> On Thu, Oct 30, 2014 at 4:51 AM, Richard Biener
> wrote:
> > On Wed, Oct 29, 2014 at 6:13 PM, David Edelsohn wrote:
> >> On Wed, Oct 29, 2014 at 9:24 AM, Richard Biener
> >> wrote:
> >>
> >>> Because only genmatch calls functions from libstdc++. Btw
On Thu, Oct 30, 2014 at 4:51 AM, Richard Biener
wrote:
> On Wed, Oct 29, 2014 at 6:13 PM, David Edelsohn wrote:
>> On Wed, Oct 29, 2014 at 9:24 AM, Richard Biener
>> wrote:
>>
>>> Because only genmatch calls functions from libstdc++. Btw, why
>>> would genmatch miscompile an empty function or t
On Wed, Oct 29, 2014 at 6:13 PM, David Edelsohn wrote:
> On Wed, Oct 29, 2014 at 9:24 AM, Richard Biener
> wrote:
>
>> Because only genmatch calls functions from libstdc++. Btw, why
>> would genmatch miscompile an empty function or the call to it?
>
> I tried bootstrapping with libstdc++ built w
On Wed, Oct 29, 2014 at 9:24 AM, Richard Biener
wrote:
> Because only genmatch calls functions from libstdc++. Btw, why
> would genmatch miscompile an empty function or the call to it?
I tried bootstrapping with libstdc++ built without the AIX ld "-G"
flag and that is succeeding.
"-G" produces
On Wed, Oct 29, 2014 at 2:10 PM, David Edelsohn wrote:
> On Wed, Oct 29, 2014 at 8:26 AM, Richard Biener wrote:
>> On Fri, 24 Oct 2014, David Edelsohn wrote:
>>
>>> genmatch is hanging when bootstrapping on AIX (gcc111). When I attach
>>> to the process:
>>>
>>> #0 0x1007efac in std::basic_stri
On Wed, Oct 29, 2014 at 8:26 AM, Richard Biener wrote:
> On Fri, 24 Oct 2014, David Edelsohn wrote:
>
>> genmatch is hanging when bootstrapping on AIX (gcc111). When I attach
>> to the process:
>>
>> #0 0x1007efac in std::basic_string,
>> std::allocator >::basic_string ()
>> #1 0x1000e6b0 in _Z
On Fri, 24 Oct 2014, David Edelsohn wrote:
> genmatch is hanging when bootstrapping on AIX (gcc111). When I attach
> to the process:
>
> #0 0x1007efac in std::basic_string,
> std::allocator >::basic_string ()
> #1 0x1000e6b0 in _ZN6parser13parse_captureEP7operand (this=0x300594b8,
> op=0x0)
>
On Mon, 27 Oct 2014, David Edelsohn wrote:
> Richi,
>
> The bootstrap with an empty match.pd seems to be succeeding. I don't
> know if you have disabled optimizations in other passes that now are
> implemented in genmatch. Regular testing of AIX is important to
> discover bootstrap issues early
Richi,
The bootstrap with an empty match.pd seems to be succeeding. I don't
know if you have disabled optimizations in other passes that now are
implemented in genmatch. Regular testing of AIX is important to
discover bootstrap issues early and avoid more release blocking
issues.
AIX and PPC64
On October 27, 2014 8:13:09 PM CET, David Edelsohn wrote:
>On Mon, Oct 27, 2014 at 2:37 AM, Richard Biener
> wrote:
>> On October 27, 2014 1:49:54 AM CET, David Edelsohn
> wrote:
>>>Richi,
>>>
>>>Does genmatch rely on static constructors or implicitly rely on the
>>>order of static constructors? S
On Mon, Oct 27, 2014 at 2:37 AM, Richard Biener
wrote:
> On October 27, 2014 1:49:54 AM CET, David Edelsohn wrote:
>>Richi,
>>
>>Does genmatch rely on static constructors or implicitly rely on the
>>order of static constructors? Sometimes those cause problems on AIX.
>
> No, it doesn't.
>
>>Boots
On Mon, Oct 27, 2014 at 2:37 AM, Richard Biener
wrote:
> On October 27, 2014 1:49:54 AM CET, David Edelsohn wrote:
>>Richi,
>>
>>Does genmatch rely on static constructors or implicitly rely on the
>>order of static constructors? Sometimes those cause problems on AIX.
>
> No, it doesn't.
>
>>Boots
On Mon, Oct 27, 2014 at 2:37 AM, Richard Biener
wrote:
> On October 27, 2014 1:49:54 AM CET, David Edelsohn wrote:
>>Richi,
>>
>>Does genmatch rely on static constructors or implicitly rely on the
>>order of static constructors? Sometimes those cause problems on AIX.
>
> No, it doesn't.
>
>>Boots
On October 27, 2014 1:49:54 AM CET, David Edelsohn wrote:
>Richi,
>
>Does genmatch rely on static constructors or implicitly rely on the
>order of static constructors? Sometimes those cause problems on AIX.
No, it doesn't.
>Bootstrap on AIX succeeds prior to r216631, e.g., r216624. It works
>af
Richi,
Does genmatch rely on static constructors or implicitly rely on the
order of static constructors? Sometimes those cause problems on AIX.
Bootstrap on AIX succeeds prior to r216631, e.g., r216624. It works
after your commit r216619 to correct Makefile.in, or prior to that by
manually editi
On October 26, 2014 12:26:29 AM CEST, David Edelsohn wrote:
>Richard,
>
>I confirmed again with gcc111, which fails with r216632 and succeeds
>with r216624.
Can you revert r216631 but still keep the r216632 fix? I suppose bootstrap
before r216632 still fails on AIX?
I'll try to reproduce on ppc
Richard,
I confirmed again with gcc111, which fails with r216632 and succeeds
with r216624.
On my internal AIX system bootstrapping with GCC 4.7.3, it enters an
infinite loop in stage 1. With gcc111 and bootstrapping with GCC
4.8.1, it enters an infinite loop in stage 2.
Thanks, David
On Sat,
Bootstrap succeeds with Maxim's patch (r216624).
The other, significant changes I see on trunk between r216624 and r216674 are:
match-and-simplify through r216632
ipc-icf in r216662
libstdc++ in r216667
No other patches to trunk *seem* like they should affect PPC bootstrap.
- David
On Sat, Oc
It may be fallout from Maxim's scheduler patch. I'm testing that.
Backing up before Maxim's patch and your genmatch patch does not enter
an endless loop.
- David
On Sat, Oct 25, 2014 at 4:06 AM, Richard Biener wrote:
> On October 25, 2014 1:33:39 AM CEST, David Edelsohn wrote:
>>genmatch is ha
This occurs in genmatch builti in stage2. Revision 216674.
Because of the previous build breakage during the merge, it is
difficult to know exactly what was working. GCC seemed to be able to
build with the earlier genmatch patch.
Running genmatch --gimple match.pd produces no output and spins i
On October 25, 2014 1:33:39 AM CEST, David Edelsohn wrote:
>genmatch is hanging when bootstrapping on AIX (gcc111). When I attach
>to the process:
>
>#0 0x1007efac in std::basic_string,
>std::allocator >::basic_string ()
>#1 0x1000e6b0 in _ZN6parser13parse_captureEP7operand (this=0x300594b8,
>o
genmatch is hanging when bootstrapping on AIX (gcc111). When I attach
to the process:
#0 0x1007efac in std::basic_string,
std::allocator >::basic_string ()
#1 0x1000e6b0 in _ZN6parser13parse_captureEP7operand (this=0x300594b8, op=0x0)
at /home/dje/src/src/gcc/genmatch.c:2607
#2 0x1000e9f0
22 matches
Mail list logo