public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andris Pavenis <andris.pavenis@iki.fi>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Arnaud Charlet <charlet@adacore.com>,
	DJ Delorie <dj@delorie.com>
Subject: Re: [PATCH 3/4][Ada,DJGPP] Ada support for DJGPP
Date: Wed, 14 Sep 2016 03:47:00 -0000	[thread overview]
Message-ID: <8d9c0d18-9c2b-8938-b649-82bb85c662bf@iki.fi> (raw)
In-Reply-To: <1695281.HKxou3PN56@arcturus.home>

On 09/13/2016 11:39 PM, Eric Botcazou wrote:
>> Found that the first revision causing this problem (of course with DJGPP
>> related patches applied) is 239113. Native bootstrap with same DJGPP
>> related patches applied on top of revision 239112 succeeds without
>> problems.
>>
>> [andris@ap gcc]$ git bisect good
>> 4bfa373ed2bfd022628609751ff34b8e51e0c2b9 is the first bad commit
>> commit 4bfa373ed2bfd022628609751ff34b8e51e0c2b9
>> Author: kugan <kugan@138bc75d-0d04-0410-961f-82ee72b054a4>
>> Date:   Thu Aug 4 04:20:01 2016 +0000
>>
>>       gcc/ChangeLog:
>>
>>       2016-08-04  Kugan Vivekanandarajah<kuganv@linaro.org>
>>
>>           * tree-vrp.c (set_value_range): Use vrp_equiv_obstack with
>>           BITMAP_ALLOC.
>>           (add_equivalence): Likewise.
>>           (get_value_range): Allocate value range with vrp_value_range_pool.
>>           (vrp_initialize): Initialize vrp_equiv_obstack for equiv
>> allocation. (vrp_finalize): Relase vrp_equiv_obstack and
>> vrp_value_range_pool.
> Ugh, this looks like a memory corruption issue.
>
Thanks for good hint.

Problem solved (fixed stack size for gnat1.exe was insufficient after mentioned change). Increasing 
it causes problem to go away. I'll recheck with full native DJGPP bootstrap. Currently only quick 
test done (by editing stack size of 3rd stage gnat1.exe).

Andris


  reply	other threads:[~2016-09-14  3:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30  5:46 Andris Pavenis
2016-08-18  9:42 ` Arnaud Charlet
2016-08-22  4:04   ` Andris Pavenis
2016-08-25  9:46     ` Arnaud Charlet
2016-09-04 17:10       ` Andris Pavenis
2016-09-04 18:52         ` Arnaud Charlet
2016-09-05  5:26           ` Andris Pavenis
2016-09-05  6:42             ` Arnaud Charlet
2016-09-14 16:16               ` Andris Pavenis
2016-09-05  7:21             ` Eric Botcazou
2016-09-07 18:16               ` Andris Pavenis
2016-09-13 16:34                 ` Andris Pavenis
2016-09-14  0:15                   ` Eric Botcazou
2016-09-14  3:47                     ` Andris Pavenis [this message]
2016-10-10 15:55         ` [PING][PATCH " Andris Pavenis
2016-10-11  8:46           ` Arnaud Charlet
2016-10-11 18:42             ` Andris Pavenis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d9c0d18-9c2b-8938-b649-82bb85c662bf@iki.fi \
    --to=andris.pavenis@iki.fi \
    --cc=charlet@adacore.com \
    --cc=dj@delorie.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).