<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - DragonEgg 3.6 build failure"
href="https://llvm.org/bugs/show_bug.cgi?id=22925">22925</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>DragonEgg 3.6 build failure
</td>
</tr>
<tr>
<th>Product</th>
<td>dragonegg
</td>
</tr>
<tr>
<th>Version</th>
<td>3.6
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>release blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>New Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>baldrick@free.fr
</td>
</tr>
<tr>
<th>Reporter</th>
<td>rcgorton@cognitive-electronics.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>I'm hitting the following compilation error with dragonegg-3.6.0 && llvm-3.6.0
on Linux.
-bash-4.1$ make
Compiling Aliasing.cpp
/home/rcgorton/svn/Compiler/trunk/LLVM3_6/dragonegg-3.6.0.src/src/Aliasing.cpp:
In function ‘llvm::MDNode* describeAliasSet(tree)’:
/home/rcgorton/svn/Compiler/trunk/LLVM3_6/dragonegg-3.6.0.src/src/Aliasing.cpp:140:16:
error: ‘class llvm::MDNode’ has no member named ‘replaceAllUsesWith’
LeafTag->replaceAllUsesWith(getTBAARoot());
^
make: *** [Aliasing.o] Error 1
--------
In LLVM3.5, MDNode is jointly derived from public Value, public FoldingSetNode;
the method replaceAllUsesWith() is part of class Value.
In LLVM3.6, MDNode is derived from public Metadata; the Metadata class does not
have such a method.
If I understand the LLVM3.6 release notes correctly, Metadata nodes do not have
use-lists, but the Aliasing.cpp code appears to require use lists.
Unfortunately, I do not know enough about Metadata to be able to effect a
patch/fix.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>