<?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 macho-invalid-thread-count-wrong</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>210030ba - Next set of additional error checks for invalid Mach-O files for the</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Object/Inputs/macho-invalid-thread-count-wrong#210030ba</link>
        <description>Next set of additional error checks for invalid Mach-O files for theload commands that use the MachO::thread_command typebut are not used in llvm libObject code but used in llvm tool code.This includes the LC_UNIXTHREAD and LC_THREADload commands.A quick note about the philosophy of the error checking inlibObject for Mach-O files, the idea behind the checking isthat we never will return a Mach-O file out of libObject thatcontains unknown things in the load commands.To do this the 32-bit ARM and PPC general tread statesneeded to be defined as two test case binaries containedthem.  If other thread states for other CPUs need to beadded we will do that as needed.Going forward the LC_MAIN load command is used toset the entry point in Mach-O executables these daysinstead of an LC_UNIXTHREAD as was done in the past.So today only in core files are LC_THREAD load commandsand thread states usually found.Other thread states have not yet been defined ininclude/Support/MachO.h at this time.  But that can beadded as needed with their corresponding checking alsoadded.llvm-svn: 284668

            List of files:
            /llvm-project-15.0.7/llvm/test/Object/Inputs/macho-invalid-thread-count-wrong</description>
        <pubDate>Wed, 19 Oct 2016 23:44:34 +0000</pubDate>
        <dc:creator>Kevin Enderby &lt;enderby@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
