From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97917] Talos Principle gives Assertion `!NodePtr->isKnownSentinel()' failed
Date: Sun, 25 Sep 2016 03:20:15 +0000 [thread overview]
Message-ID: <bug-97917-502-aV3iosWEsM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97917-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97917
Vedran Miletić <vedran@miletic.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |77449
Keywords| |regression
--- Comment #1 from Vedran Miletić <vedran@miletic.net> ---
6037e199c8a061b2e9cb22c434644a0eac659fb9 is the first bad commit
commit 6037e199c8a061b2e9cb22c434644a0eac659fb9
Author: Duncan P. N. Exon Smith <dexonsmith@apple.com>
Date: Sun Sep 11 16:38:18 2016 +0000
CodeGen: Turn on sentinel tracking for MachineInstr iterators
This is a prep commit before fixing MachineBasicBlock::reverse_iterator
invalidation semantics, ala r281167 for ilist::reverse_iterator. This
changes MachineBasicBlock::Instructions to track which node is the
sentinel regardless of LLVM_ENABLE_ABI_BREAKING_CHECKS.
There's almost no functionality change (aside from ABI). However, in
the rare configuration:
#if !defined(NDEBUG) && !defined(LLVM_ENABLE_ABI_BREAKING_CHECKS)
the isKnownSentinel() assertions in ilist_iterator<>::operator* suddenly
have teeth for MachineInstr. If these assertions start firing for your
out-of-tree backend, have a look at the suggestions in the commit
message for r279314, and at some of the commits leading up to it that
avoid dereferencing the end() iterator.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@281168
91177308-0d34-0410-b5e6-96231b3b80d8
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=77449
[Bug 77449] Tracker bug for all bugs related to Steam titles
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3856 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-25 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:12 [Bug 97917] Talos Principle gives Assertion `!NodePtr->isKnownSentinel()' failed bugzilla-daemon
2016-09-25 3:20 ` bugzilla-daemon [this message]
2016-09-25 3:24 ` bugzilla-daemon
2016-09-25 9:37 ` bugzilla-daemon
2016-09-26 19:04 ` bugzilla-daemon
2016-09-27 21:34 ` bugzilla-daemon
2016-09-27 21:40 ` [Bug 97917] Enabling sisched " bugzilla-daemon
2016-09-28 10:31 ` bugzilla-daemon
2017-01-25 19:41 ` bugzilla-daemon
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-97917-502-aV3iosWEsM@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 NNTP newsgroup(s).