<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in vortex-bug.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2f448bf5 - [X86] Migrate tests to use opaque pointers (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#2f448bf5</link>
        <description>[X86] Migrate tests to use opaque pointers (NFC)Test updates were performed using:https://gist.github.com/nikic/98357b71fd67756b0f064c9517b62a34These are only the test updates where the test passed withoutfurther modification (which is almost all of them, as the backendis largely pointer-type agnostic).

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Wed, 22 Jun 2022 12:33:12 +0000</pubDate>
        <dc:creator>Nikita Popov &lt;npopov@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>6b898beb - X86: Do not use llc -march in tests.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#6b898beb</link>
        <description>X86: Do not use llc -march in tests.`llc -march` is problematic because it only switches the targetarchitecture, but leaves the operating system unchanged. Thisoccasionally leads to indeterministic tests because the OS fromLLVM_DEFAULT_TARGET_TRIPLE is used.However we can simply always use `llc -mtriple` instead. This changesall the tests to do this to avoid people using -march when they copy andpaste parts of tests.See also the discussion in https://reviews.llvm.org/D35287llvm-svn: 309774

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Wed, 02 Aug 2017 00:28:10 +0000</pubDate>
        <dc:creator>Matthias Braun &lt;matze@braunis.de&gt;</dc:creator>
    </item>
<item>
        <title>79e6c749 - [opaque pointer type] Add textual IR support for explicit type parameter to getelementptr instruction</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#79e6c749</link>
        <description>[opaque pointer type] Add textual IR support for explicit type parameter to getelementptr instructionOne of several parallel first steps to remove the target type of pointers,replacing them with a single opaque pointer type.This adds an explicit type parameter to the gep instruction so that when thefirst parameter becomes an opaque pointer type, the type to gep through isstill available to the instructions.* This doesn&apos;t modify gep operators, only instructions (operators will be  handled separately)* Textual IR changes only. Bitcode (including upgrade) and changing the  in-memory representation will be in separate changes.* geps of vectors are transformed as:    getelementptr &lt;4 x float*&gt; %x, ...  -&gt;getelementptr float, &lt;4 x float*&gt; %x, ...  Then, once the opaque pointer type is introduced, this will ultimately look  like:    getelementptr float, &lt;4 x ptr&gt; %x  with the unambiguous interpretation that it is a vector of pointers to float.* address spaces remain on the pointer, not the type:    getelementptr float addrspace(1)* %x  -&gt;getelementptr float, float addrspace(1)* %x  Then, eventually:    getelementptr float, ptr addrspace(1) %xImportantly, the massive amount of test case churn has been automated bysame crappy python code. I had to manually update a few test cases thatwouldn&apos;t fit the script&apos;s model (r228970,r229196,r229197,r229198). Thepython script just massages stdin and writes the result to stdout, Ithen wrapped that in a shell script to handle replacing files, thenusing the usual find+xargs to migrate all the files.update.py:import fileinputimport sysimport reibrep = re.compile(r&quot;(^.*?[^%\w]getelementptr inbounds )(((?:&lt;\d* x )?)(.*?)(| addrspace\(\d\)) *\*(|&gt;)(?:$| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$))&quot;)normrep = re.compile(       r&quot;(^.*?[^%\w]getelementptr )(((?:&lt;\d* x )?)(.*?)(| addrspace\(\d\)) *\*(|&gt;)(?:$| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$))&quot;)def conv(match, line):  if not match:    return line  line = match.groups()[0]  if len(match.groups()[5]) == 0:    line += match.groups()[2]  line += match.groups()[3]  line += &quot;, &quot;  line += match.groups()[1]  line += &quot;\n&quot;  return linefor line in sys.stdin:  if line.find(&quot;getelementptr &quot;) == line.find(&quot;getelementptr inbounds&quot;):    if line.find(&quot;getelementptr inbounds&quot;) != line.find(&quot;getelementptr inbounds (&quot;):      line = conv(re.match(ibrep, line), line)  elif line.find(&quot;getelementptr &quot;) != line.find(&quot;getelementptr (&quot;):    line = conv(re.match(normrep, line), line)  sys.stdout.write(line)apply.sh:for name in &quot;$@&quot;do  python3 `dirname &quot;$0&quot;`/update.py &lt; &quot;$name&quot; &gt; &quot;$name.tmp&quot; &amp;&amp; mv &quot;$name.tmp&quot; &quot;$name&quot;  rm -f &quot;$name.tmp&quot;doneThe actual commands:From llvm/src:find test/ -name *.ll | xargs ./apply.shFrom llvm/src/tools/clang:find test/ -name *.mm -o -name *.m -o -name *.cpp -o -name *.c | xargs -I &apos;{}&apos; ../../apply.sh &quot;{}&quot;From llvm/src/tools/polly:find test/ -name *.ll | xargs ./apply.shAfter that, check-all (with llvm, clang, clang-tools-extra, lld,compiler-rt, and polly all checked out).The extra &apos;rm&apos; in the apply.sh script is due to a few files in clang&apos;s testsuite using interesting unicode stuff that my python script was throwingexceptions on. None of those files needed to be migrated, so it seemedsufficient to ignore those cases.Reviewers: rafael, dexonsmith, grosserDifferential Revision: http://reviews.llvm.org/D7636llvm-svn: 230786

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Fri, 27 Feb 2015 19:29:02 +0000</pubDate>
        <dc:creator>David Blaikie &lt;dblaikie@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>40503396 - Eliminate more uses of llvm-as and llvm-dis.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#40503396</link>
        <description>Eliminate more uses of llvm-as and llvm-dis.llvm-svn: 81290

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Tue, 08 Sep 2009 23:54:48 +0000</pubDate>
        <dc:creator>Dan Gohman &lt;gohman@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>cd2e772d - Run vortex-bug as x86-64, which is what the original bug was triggered on.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#cd2e772d</link>
        <description>Run vortex-bug as x86-64, which is what the original bug was triggered on.llvm-svn: 51289

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Tue, 20 May 2008 00:54:39 +0000</pubDate>
        <dc:creator>Dan Gohman &lt;gohman@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>0a0fa7cf - Fix a bug in LoopStrengthReduce that caused it to emit IR with</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll#0a0fa7cf</link>
        <description>Fix a bug in LoopStrengthReduce that caused it to emit IR withuse-before-def. The problem comes up in code with multiple PHIs whereone PHI is being rewritten in terms of the other, but the other needsto be casted first. LLVM rules requre the cast instruction to beinserted after any PHI instructions, but when instructions wereinserted to replace the second PHI value with a function of the first,they were ended up going before the cast instruction. Avoid thisproblem by remembering the location of the cast instruction, when oneis needed, and inserting the expansion of the new value after it.This fixes a bug that surfaced in 255.vortex on x86-64 wheninstcombine was removed from the middle of the loop optimizationpasses. llvm-svn: 51169

            List of files:
            /llvm-project-15.0.7/llvm/test/CodeGen/X86/vortex-bug.ll</description>
        <pubDate>Thu, 15 May 2008 23:26:57 +0000</pubDate>
        <dc:creator>Dan Gohman &lt;gohman@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
