From: Steve Ellcey <sellcey@marvell.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, "law@redhat.com" <law@redhat.com>
Subject: Re: Help with bug in GCC garbage collector
Date: Mon, 19 Aug 2019 23:25:00 -0000 [thread overview]
Message-ID: <e31cf63e12abd77dcafa2d76bc232e116c03969f.camel@marvell.com> (raw)
In-Reply-To: <5bd227e3-af73-145e-9bd6-88560e6509a4@redhat.com>
On Mon, 2019-08-19 at 17:05 -0600, Jeff Law wrote:
>
> There's a real good chance Martin Liska has already fixed this. He's
> made a couple fixes in the last week or so with the interactions
> between
> the GC system and the symbol tables.
>
>
> 2019-08-15 Martin Liska <mliska@suse.cz>
>
> PR ipa/91404
> * passes.c (order): Remove.
> (uid_hash_t): Likewise).
> (remove_cgraph_node_from_order): Remove from set
> of pointers (cgraph_node *).
> (insert_cgraph_node_to_order): New.
> (duplicate_cgraph_node_to_order): New.
> (do_per_function_toporder): Register all 3 cgraph hooks.
> Skip removed_nodes now as we know about all of them.
>
>
> The way I'd approach would be to configure a compiler with
> --enable-checking=gc,gcac, just build it through stage1. Then run your
> test through that compiler which should fail. THen apply Martin's patch
> (or update to the head of the trunk), rebuild the stage1 compiler and
> verify it works.
I had already built a compiler with --enable-checking=gc,gcac, that did
not catch the bug (I still got a segfault). I did update my sources
though and the bug does not happen at ToT so it looks like Martin's
patch did fix my bug.
Steve Ellcey
sellcey@marvell.com
prev parent reply other threads:[~2019-08-19 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 22:59 Steve Ellcey
2019-08-19 23:05 ` Jeff Law
2019-08-19 23:25 ` Steve Ellcey [this message]
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=e31cf63e12abd77dcafa2d76bc232e116c03969f.camel@marvell.com \
--to=sellcey@marvell.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
/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).