public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/66714] ICE in loc_list_from_tree with -g
Date: Sat, 04 Jul 2015 08:34:00 -0000 [thread overview]
Message-ID: <bug-66714-4-RX7He9rRBI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66714-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66714
vries at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |6.0
Summary|gomp4: |ICE in loc_list_from_tree
|libgomp.oacc-c-c++-common/a |with -g
|tomic_capture-1.c -g ICE |
--- Comment #13 from vries at gcc dot gnu.org ---
(In reply to vries from comment #12)
> Created attachment 35908 [details]
> patch to be more aggressive in gt_cleare_cache
>
> Using this patch, we can trigger the problem with minimal testcase, and also
> for openmp:
This is a trunk patch, not a gomp-4-0-branch patch.
next prev parent reply other threads:[~2015-07-04 8:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 22:17 [Bug debug/66714] New: gomp4: libgomp.oacc-c-c++-common/atomic_capture-1.c -g ICE vries at gcc dot gnu.org
2015-07-02 11:11 ` [Bug debug/66714] " vries at gcc dot gnu.org
2015-07-02 11:21 ` vries at gcc dot gnu.org
2015-07-02 11:26 ` vries at gcc dot gnu.org
2015-07-02 11:32 ` vries at gcc dot gnu.org
2015-07-02 11:35 ` vries at gcc dot gnu.org
2015-07-02 11:39 ` vries at gcc dot gnu.org
2015-07-02 11:46 ` vries at gcc dot gnu.org
2015-07-02 11:58 ` vries at gcc dot gnu.org
2015-07-02 12:00 ` vries at gcc dot gnu.org
2015-07-04 8:26 ` vries at gcc dot gnu.org
2015-07-04 8:34 ` vries at gcc dot gnu.org [this message]
2015-07-06 7:44 ` [Bug debug/66714] ICE in loc_list_from_tree with -g vries at gcc dot gnu.org
2015-07-06 7:50 ` vries at gcc dot gnu.org
2015-07-06 7:56 ` [Bug libgomp/66714] " vries at gcc dot gnu.org
2015-07-06 9:34 ` vries at gcc dot gnu.org
2015-07-06 9:35 ` vries at gcc dot gnu.org
2015-07-09 11:12 ` vries at gcc dot gnu.org
2015-07-21 22:27 ` cesar at gcc dot gnu.org
2015-07-21 22:47 ` vries at gcc dot gnu.org
2015-07-22 2:15 ` cesar at gcc dot gnu.org
2015-07-22 23:36 ` cesar at gcc dot gnu.org
2015-07-24 14:39 ` cesar at gcc dot gnu.org
2015-07-27 14:29 ` cesar at gcc dot gnu.org
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=bug-66714-4-RX7He9rRBI@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).