<?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 ARMTargetStreamer.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>15d82c62 - [MC] De-capitalize MCStreamer functions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#15d82c62</link>
        <description>[MC] De-capitalize MCStreamer functionsFollow-up to c031378ce01b8485ba0ef486654bc9393c4ac024 .The class is mostly consistent now.

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 07 Jun 2022 07:31:02 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;i@maskray.me&gt;</dc:creator>
    </item>
<item>
        <title>6b75a352 - [ARM] [MC] Add support for writing ARM WinEH unwind info</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#6b75a352</link>
        <description>[ARM] [MC] Add support for writing ARM WinEH unwind infoThis includes .seh_* directives for generating it from assembly.It is designed fairly similarly to the ARM64 handling.For .seh_handler directives, such as&quot;.seh_handler __C_specific_handler, @except&quot; (which is supportedon x86_64 and aarch64 so far), the &quot;@except&quot; bit doesn&apos;t work inARM assembly, as &apos;@&apos; is used as a comment character (on all currentplatforms).Allow using &apos;%&apos; instead of &apos;@&apos; for this purpose. This conventionis used by GAS in similar contexts already,e.g. [1]:    Note on targets where the @ character is the start of a comment    (eg ARM) then another character is used instead. For example the    ARM port uses the % character.In practice, this unfortunately means that all such .seh_handlerdirectives will need ifdefs for ARM.Contrary to ARM64, on ARM, it&apos;s quite common that we can&apos;t evaluatee.g. the function length at this point, due to instructions whoselength is finalized later. (Also, inline jump tables end witha &quot;.p2align 1&quot;.)If unable to to evaluate the function length immediately, emitit as an MCExpr instead. If we&apos;d implement splitting the unwindinfo for a function (which isn&apos;t implemented for ARM64 yet either),we wouldn&apos;t know whether we need to split it though.Avoid calling getFrameIndexOffset() on an unsetFuncInfo.UnwindHelpFrameIdx, to avoid triggering asserts in thepreexisting testcase CodeGen/ARM/Windows/wineh-basic.ll. (OnceMSVC exception handling is fully implemented, those changescan be reverted.)[1] https://sourceware.org/binutils/docs/as/Section.html#SectionDifferential Revision: https://reviews.llvm.org/D125645

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Thu, 11 Nov 2021 10:06:49 +0000</pubDate>
        <dc:creator>Martin Storsj&#246; &lt;martin@martin.st&gt;</dc:creator>
    </item>
<item>
        <title>051deb2d - [ARM] add Armv9 build attribute</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#051deb2d</link>
        <description>[ARM] add Armv9 build attributeThe build attribute number can be found in the Arm ABI addenda32 document:https://github.com/ARM-software/abi-aa/blob/main/addenda32/addenda32.rst#335target-related-attributesReviewed By: tmathesonDifferential Revision: https://reviews.llvm.org/D124090

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Thu, 28 Apr 2022 09:23:54 +0000</pubDate>
        <dc:creator>Ties Stuij &lt;ties@stuij.se&gt;</dc:creator>
    </item>
<item>
        <title>b430782b - [ARM] emit PACBTI-M build attributes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#b430782b</link>
        <description>[ARM] emit PACBTI-M build attributesThis patch is part of a series that adds support for the PACBTI-M extension ofthe Armv8.1-M architecture, as detailed here:https://community.arm.com/arm-community-blogs/b/architectures-and-processors-blog/posts/armv8-1-m-pointer-authentication-and-branch-target-identification-extensionThe PACBTI-M specification can be found in the Armv8-M Architecture ReferenceManual:https://developer.arm.com/documentation/ddi0553/latestThe following people contributed to this patch:- Victor Campos- Ties StuijReviewed By: ostannardDifferential Revision: https://reviews.llvm.org/D112425

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Wed, 01 Dec 2021 10:52:31 +0000</pubDate>
        <dc:creator>Ties Stuij &lt;ties.stuij@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>ad253446 - [MC][CodeGen] Emit constant pools earlier</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#ad253446</link>
        <description>[MC][CodeGen] Emit constant pools earlierPreviously we would emit constant pool entries for ldr inline asm at thevery end of AsmPrinter::doFinalization(). However, if we&apos;re emittingdwarf aranges, that would end all sections with aranges. Then if we haveconstant pool entries to be emitted in those same sections, we&apos;d hit anassert that the section has already been ended.We want to emit constant pool entries before emitting dwarf aranges.This patch splits out arm32/64&apos;s constant pool entry emission into itsown MCTargetStreamer virtual method.Fixes PR51208Reviewed By: MaskRayDifferential Revision: https://reviews.llvm.org/D107314

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Mon, 02 Aug 2021 22:33:07 +0000</pubDate>
        <dc:creator>Arthur Eubanks &lt;aeubanks@google.com&gt;</dc:creator>
    </item>
<item>
        <title>a55daa14 - [MC] De-capitalize some MCStreamer::Emit* functions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#a55daa14</link>
        <description>[MC] De-capitalize some MCStreamer::Emit* functions

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Sat, 15 Feb 2020 02:16:24 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>65b3b6c0 - [ARM] Make ARM::ArchExtKind use 64-bit underlying type (part 2), NFCI</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#65b3b6c0</link>
        <description>[ARM] Make ARM::ArchExtKind use 64-bit underlying type (part 2), NFCISummary:After following Simon&apos;s suggestion about additional testing posted athttps://reviews.llvm.org/D73906, I found several more places thatneed to be updated.Reviewers: simon_tatham, dmgreen, ostannard, eli.friedmanReviewed By: simon_tathamSubscribers: merge_guards_bot, kristof.beyls, hiraditya, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D73963

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 04 Feb 2020 14:48:10 +0000</pubDate>
        <dc:creator>Mikhail Maltsev &lt;mikhail.maltsev@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>ddf5e86c - [ARM] VFPv2 only supports 16 D registers.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#ddf5e86c</link>
        <description>[ARM] VFPv2 only supports 16 D registers.r361845 changed the way we handle &quot;D16&quot; vs. &quot;D32&quot; targets; there used tobe a negative &quot;d16&quot; which removed instructions from the instruction set,and now there&apos;s a &quot;d32&quot; feature which adds instructions to theinstruction set.  This is good, but there was an oversight in theimplementation: the behavior of VFPv2 was changed.  In particular, the&quot;vfp2&quot; feature was changed to imply &quot;d32&quot;. This is wrong: VFPv2 onlysupports 16 D registers.In practice, this means if you specify -mfpu=vfpv2, the compiler willgenerate illegal instructions.This patch gets rid of &quot;vfp2d16&quot; and &quot;vfp2d16sp&quot;, and fixes &quot;vfp2&quot; and&quot;vfp2sp&quot; so they don&apos;t imply &quot;d32&quot;.Differential Revision: https://reviews.llvm.org/D67375llvm-svn: 372186

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 17 Sep 2019 21:42:38 +0000</pubDate>
        <dc:creator>Eli Friedman &lt;efriedma@quicinc.com&gt;</dc:creator>
    </item>
<item>
        <title>930dee2c - [ARM] add target arch definitions for 8.1-M and MVE</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#930dee2c</link>
        <description>[ARM] add target arch definitions for 8.1-M and MVEThis adds:- LLVM subtarget features to make all the new instructions conditional on,- CPU and FPU names for use on clang&apos;s command line, with default FPUs set  so that &quot;armv8.1-m.main+fp&quot; and &quot;armv8.1-m.main+fp.dp&quot; will select the right  FPU features,- architecture extension names &quot;mve&quot; and &quot;mve.fp&quot;,- ABI build attribute support for v8.1-M (a new value for Tag_CPU_arch) and MVE  (a new actual tag).Patch mostly by Simon Tatham.Differential Revision: https://reviews.llvm.org/D60698llvm-svn: 362090

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Thu, 30 May 2019 12:57:04 +0000</pubDate>
        <dc:creator>Sjoerd Meijer &lt;sjoerd.meijer@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>760df47b - [ARM] Replace fp-only-sp and d16 with fp64 and d32.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#760df47b</link>
        <description>[ARM] Replace fp-only-sp and d16 with fp64 and d32.Those two subtarget features were awkward because their semantics arereversed: each one indicates the _lack_ of support for something inthe architecture, rather than the presence. As a consequence, youdon&apos;t get the behavior you want if you combine two sets of featurebits.Each SubtargetFeature for an FP architecture version now comes in fourversions, one for each combination of those options. So you can stillsay (for example) &apos;+vfp2&apos; in a feature string and it will mean whatit&apos;s always meant, but there&apos;s a new string &apos;+vfp2d16sp&apos; meaning theversion without those extra options.A lot of this change is just mechanically replacing positive checksfor the old features with negative checks for the new ones. But onemore interesting change is that I&apos;ve rearranged getFPUFeatures() sothat the main FPU feature is appended to the output list *before*rather than after the features derived from the Restriction field, sothat -fp64 and -d32 can override defaults added by the main feature.Reviewers: dmgreen, samparker, SjoerdMeijerSubscribers: srhines, javed.absar, eraman, kristof.beyls, hiraditya, zzheng, Petar.Avramovic, cfe-commits, llvm-commitsTags: #clang, #llvmDifferential Revision: https://reviews.llvm.org/D60691llvm-svn: 361845

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 28 May 2019 16:13:20 +0000</pubDate>
        <dc:creator>Simon Tatham &lt;simon.tatham@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>2946cd70 - Update the file headers across all of the LLVM projects in the monorepo</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#2946cd70</link>
        <description>Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we&apos;re moving the headerentirely to discuss the new license. We checked this carefully with theFoundation&apos;s lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Sat, 19 Jan 2019 08:50:56 +0000</pubDate>
        <dc:creator>Chandler Carruth &lt;chandlerc@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>27c769d2 - [Target] Untangle disassemblers</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#27c769d2</link>
        <description>[Target] Untangle disassemblersDisassemblers cannot depend on main target headers. The same is true forMCTargetDesc, but there&apos;s a lot more cleanup needed for that.llvm-svn: 341822

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Mon, 10 Sep 2018 12:53:46 +0000</pubDate>
        <dc:creator>Benjamin Kramer &lt;benny.kra@googlemail.com&gt;</dc:creator>
    </item>
<item>
        <title>af18947f - [ARM] Support the .inst directive for MachO and COFF targets</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#af18947f</link>
        <description>[ARM] Support the .inst directive for MachO and COFF targetsContrary to ELF, we don&apos;t add any markers that distinguish data generatedwith .short/.long from normal instructions, so the .inst directive onlyadds compatibility with assembly that uses it.Differential Revision: https://reviews.llvm.org/D49936llvm-svn: 338356

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 31 Jul 2018 09:27:01 +0000</pubDate>
        <dc:creator>Martin Storsjo &lt;martin@martin.st&gt;</dc:creator>
    </item>
<item>
        <title>67ddd1d0 - [TargetParser] Use enum classes for various ARM kind enums.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#67ddd1d0</link>
        <description>[TargetParser] Use enum classes for various ARM kind enums.Summary:Using c++11 enum classes ensures that only valid enum values are usedfor ArchKind, ProfileKind, VersionKind and ISAKind. This removes theneed for checks that the provided values map to a proper enum value,allows us to get rid of AK_LAST and prevents comparing values fromdifferent enums. It also removes a bunch of static_castfrom unsigned to enum values and vice versa, at the cost of introducingstatic casts to access AArch64ARCHNames and ARMARCHNames by ArchKind.FPUKind and ArchExtKind are the only remaining old-style enum inTargetParser.h. I think it&apos;s beneficial to keep ArchExtKind as old-styleenum, but FPUKind can be converted too, but this patch is quite big, socould do this in a follow-up patch. I could also split this patch up abit, if people would prefer that.Reviewers: rengolin, javed.absar, chandlerc, rovkaReviewed By: rovkaSubscribers: aemerson, kristof.beyls, llvm-commitsDifferential Revision: https://reviews.llvm.org/D35882llvm-svn: 309287

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Thu, 27 Jul 2017 16:27:56 +0000</pubDate>
        <dc:creator>Florian Hahn &lt;florian.hahn@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>6110be97 - Re-apply r302416: [ARM] Clear the constant pool cache on explicit .ltorg directives</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#6110be97</link>
        <description>Re-apply r302416: [ARM] Clear the constant pool cache on explicit .ltorg directivesRe-applying now that PR32825 which was raised on the commit this fixed up is now known to have also been fixed by this commit.Original commit message:    Multiple ldr pseudoinstructions with the same constant value will    reuse the same constant pool entry. However, if the constant pool    is explicitly flushed with a .ltorg directive, we should not try    to reference constants in the previous pool any longer, since they    may be out of range.    This fixes assembling hand-written assembler source which repeatedly    loads the same constant value, across a binary size larger than the    pc-relative fixup range for ldr instructions (4096 bytes). Such    assembler source already uses explicit .ltorg instructions to emit    constant pools with regular intervals. However if we try to reuse    constants emitted in earlier pools, they end up out of range.    This makes the output of the testcase match what binutils gas does    (prior to this patch, it would fail to assemble).    Differential Revision: https://reviews.llvm.org/D32847llvm-svn: 303540

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Mon, 22 May 2017 09:42:07 +0000</pubDate>
        <dc:creator>James Molloy &lt;james.molloy@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>5cc75ae8 - Revert &quot;[ARM] Clear the constant pool cache on explicit .ltorg directives&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#5cc75ae8</link>
        <description>Revert &quot;[ARM] Clear the constant pool cache on explicit .ltorg directives&quot;This reverts commit r302416. This was a fixup for r286006, which has now been reverted so this doesn&apos;t apply (either in concept or in code).This commit itself has no problems, but the underlying issue it was fixing has now disappeared from the codebase.llvm-svn: 303536

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Mon, 22 May 2017 08:49:28 +0000</pubDate>
        <dc:creator>James Molloy &lt;james.molloy@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>fd4c158a - [ARM] Clear the constant pool cache on explicit .ltorg directives</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#fd4c158a</link>
        <description>[ARM] Clear the constant pool cache on explicit .ltorg directivesMultiple ldr pseudoinstructions with the same constant value willreuse the same constant pool entry. However, if the constant poolis explicitly flushed with a .ltorg directive, we should not tryto reference constants in the previous pool any longer, since theymay be out of range.This fixes assembling hand-written assembler source which repeatedlyloads the same constant value, across a binary size larger than thepc-relative fixup range for ldr instructions (4096 bytes). Suchassembler source already uses explicit .ltorg instructions to emitconstant pools with regular intervals. However if we try to reuseconstants emitted in earlier pools, they end up out of range.This makes the output of the testcase match what binutils gas does(prior to this patch, it would fail to assemble).Differential Revision: https://reviews.llvm.org/D32847llvm-svn: 302416

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Mon, 08 May 2017 10:26:24 +0000</pubDate>
        <dc:creator>Martin Storsjo &lt;martin@martin.st&gt;</dc:creator>
    </item>
<item>
        <title>7c6dee9f - [ARM] Rename HW div feature to HW div Thumb. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#7c6dee9f</link>
        <description>[ARM] Rename HW div feature to HW div Thumb. NFCI.The hardware div feature refers only to Thumb, but because of its nameit is tempting to use it to check for hardware division in general,which may cause problems in ARM mode. See https://reviews.llvm.org/D32005.This patch adds &quot;Thumb&quot; to its name, to make its scope clear. Onenotable place where I haven&apos;t made the change is in the feature flag(used with -mattr), which is still hwdiv. Changing it would also requirechanges in a lot of tests, including clang tests, and it doesn&apos;t seemlike it&apos;s worth the effort.Differential Revision: https://reviews.llvm.org/D32160llvm-svn: 300827

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Thu, 20 Apr 2017 09:38:25 +0000</pubDate>
        <dc:creator>Diana Picus &lt;diana.picus@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>7ad2e8aa - [ARM] Add hardware build attributes in assembler</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#7ad2e8aa</link>
        <description>[ARM] Add hardware build attributes in assemblerIn the assembler, we should emit build attributes based on the targetselected with command-line options. This matches the GNU assembler&apos;sbehaviour. We only do this for build attributes which describe thehardware that is expected to be available, not the ones that describeABI compatibility.This is done by moving some of the attribute emission code toARMTargetStreamer, so that it can be shared between the assembly andcode-generation code paths. Since the assembler only creates aMCSubtargetInfo, not an ARMSubtarget, the code had to be changed tocheck raw features, and not use the convenience functions inARMSubtarget.If different attributes are later specified using the .eabi_attributedirective, then they will take precedence, as happens when the same.eabi_attribute is specified twice.This must be enabled by an option, because we don&apos;t want to do this whenparsing inline assembly. The attributes would match the ones emitted atthe start of the file, so wouldn&apos;t actually change the emitted objectfile, but the extra directives would be added to every inline assemblyblock when emitting assembly, which we&apos;d like to avoid.The majority of the changes in the build-attributes.ll test are justre-ordering the directives, because the hardware attributes are nowemitted before the ABI ones. However, I did fix one bug which I spotted:Tag_CPU_arch_profile was not being emitted for v6M.Differential revision: https://reviews.llvm.org/D31812llvm-svn: 300547

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Tue, 18 Apr 2017 12:52:35 +0000</pubDate>
        <dc:creator>Oliver Stannard &lt;oliver.stannard@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>e79c077e - [ARM] Fix some Clang-tidy modernize and Include What You Use warnings; other minor fixes (NFC).</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp#e79c077e</link>
        <description>[ARM] Fix some Clang-tidy modernize and Include What You Use warnings; other minor fixes (NFC).llvm-svn: 293348

            List of files:
            /llvm-project-15.0.7/llvm/lib/Target/ARM/MCTargetDesc/ARMTargetStreamer.cpp</description>
        <pubDate>Fri, 27 Jan 2017 23:58:02 +0000</pubDate>
        <dc:creator>Eugene Zelenko &lt;eugene.zelenko@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
