en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#b19194c0 [InstCombine] handle subobjects of constant aggregatesRemove the known limitation of the library function call folders to onlywork with top-level arrays of characters (as per the TODO comment inthe code) and allows them to also fold calls involving subobjects ofconstant aggregates such as member arrays. List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 21 Jun 2022 17:31:58 +0000 Martin Sebor <msebor@redhat.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#4ab3041a Revert "[NFC] remove explicit default value for strboolattr attribute in tests"This reverts commit bda6e5bee04c75b1f1332b4fd1ac4e8ef6c3c247.See https://lab.llvm.org/buildbot/#/builders/109/builds/15424 for instance List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Mon, 24 May 2021 17:43:40 +0000 serge-sans-paille <sguelton@redhat.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#bda6e5be [NFC] remove explicit default value for strboolattr attribute in testsSince d6de1e1a71406c75a4ea4d5a2fe84289f07ea3a1, no attributes is quivalent tosetting attribute to false.This is a preliminary commit for https://reviews.llvm.org/D99080 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Sun, 23 May 2021 11:19:23 +0000 serge-sans-paille <sguelton@redhat.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#92d3e70d [X86] Change pentium4 tuning settings and scheduler model back to their values before D83913.Clang now defaults to -march=pentium4 -mtune=generic so we don'tneed modern tune settings on pentium4. List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 26 Aug 2020 22:21:55 +0000 Craig Topper <craig.topper@intel.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#ad171d24 [X86] Change the tuning settings for pentium4 to be more modern since its the default 32-bit cpu in clangAlternative to D83897. I believe the big change here is that I removed slow unaligned memory 16Down side that it may adversely effect tuning if someone explicitly targets -march=pentium4 and expects pentium4 tuned code. Of course pentium4 is so old our default behavior with the previous settings may not have been the best either.Reviewed By: echristo, RKSimonDifferential Revision: https://reviews.llvm.org/D83913 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Thu, 16 Jul 2020 18:20:57 +0000 Craig Topper <craig.topper@intel.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#502a77f1 Migrate function attribute "no-frame-pointer-elim" to "frame-pointer"="all" as cleanups after D56351 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 24 Dec 2019 23:52:21 +0000 Fangrui Song <maskray@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#faed8516 Changing CodeView debug info type record representation in assembly files to make it more human-readable & editable & fixing bug introduced in r364987llvm-svn: 365417 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 09 Jul 2019 01:11:02 +0000 Nilanjana Basu <nilanjana.basu87@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#c0b55774 Revert Changing CodeView debug info type record representation in assembly files to make it more human-readable & editableThis reverts r364982 (git commit 2082bf28ebea76cc187b508f801122866420d9ff)llvm-svn: 364987 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 03 Jul 2019 00:51:49 +0000 Nilanjana Basu <nilanjana.basu87@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#2082bf28 Changing CodeView debug info type record representation in assembly files to make it more human-readable & editablellvm-svn: 364982 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 03 Jul 2019 00:26:23 +0000 Nilanjana Basu <nilanjana.basu87@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#e29e30b1 [llvm-readobj] Change -long-option to --long-option in tests. NFCWe use both -long-option and --long-option in tests. Switch to --long-option for consistency.In the "llvm-readelf" mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf.While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion ("s" is --section-headers in llvm-readobj but --symbols in llvm-readelf).llvm-svn: 359649 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 01 May 2019 05:27:20 +0000 Fangrui Song <maskray@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#9ea2c012 [codeview] Emit S_FRAMEPROC and use S_DEFRANGE_FRAMEPOINTER_RELSummary:Before this change, LLVM would always describe locals on the stack asbeing relative to some specific register, RSP, ESP, EBP, ESI, etc.Variables in stack memory are pretty common, so there is a specialS_DEFRANGE_FRAMEPOINTER_REL symbol for them. This change uses it toreduce the size of our debug info.On top of the size savings, there are cases on 32-bit x86 where localvariables are addressed from ESP, but ESP changes across the function.Unlike in DWARF, there is no FPO data to describe the stack adjustmentsmade to push arguments onto the stack and pop them off after the call,which makes it hard for the debugger to find the local variables inframes further up the stack.To handle this, CodeView has a special VFRAME register, whichcorresponds to the $T0 variable set by our FPO data in 32-bit. Offsetsto local variables are instead relative to this value.This is part of PR38857.Reviewers: hans, zturner, javed.absarSubscribers: aprantl, hiraditya, JDevlieghere, llvm-commitsDifferential Revision: https://reviews.llvm.org/D52217llvm-svn: 343543 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Mon, 01 Oct 2018 21:59:45 +0000 Reid Kleckner <rnk@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#bd5d7122 [codeview] Use push_macro to avoid conflicts instead of a prefixSummary:This prefix was added in r333421, and it changed our dumper output tosay things like "CVRegEAX" instead of just "EAX". That's a functionalchange that I'd rather avoid.I tested GCC, Clang, and MSVC, and all of them support #pragmapush_macro. They don't issue warnings whem the macro is not definedeither.I don't have a Mac so I can't test the real termios.h header, but Ilooked at the termios.h sources online and looked for other conflicts.I saw only the CR* macros, so those are the ones we work around.Reviewers: zturner, JDevlieghereSubscribers: hiraditya, llvm-commitsDifferential Revision: https://reviews.llvm.org/D50851llvm-svn: 339907 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Thu, 16 Aug 2018 17:34:31 +0000 Reid Kleckner <rnk@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#43dce3ed [CodeView] Add prefix to CodeView registers.Adds CVReg to CodeView register names to prevent a duplicate symbol withCR3 defined in termios.h, as suggested by Zachary on the mailing list.http://lists.llvm.org/pipermail/llvm-dev/2018-May/123372.htmlDifferential revision: https://reviews.llvm.org/D47478rdar://39863705llvm-svn: 333421 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 29 May 2018 14:35:34 +0000 Jonas Devlieghere <jonas@devlieghere.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#2c864551 [DebugInfo] Add DILabel metadata and intrinsic llvm.dbg.label.In order to set breakpoints on labels and list source code aroundlabels, we need collect debug information for labels, i.e., labelname, the function label belong, line number in the file, and theaddress label located. In order to keep these information in LLVMIR and to allow backend to generate debug information correctly.We create a new kind of metadata for labels, DILabel. The formatof DILabel is!DILabel(scope: !1, name: "foo", file: !2, line: 3)We hope to keep debug information as much as possible even thecode is optimized. So, we create a new kind of intrinsic for labelmetadata to avoid the metadata is eliminated with basic block.The intrinsic will keep existing if we keep it from optimized out.The format of the intrinsic isllvm.dbg.label(metadata !1)It has only one argument, that is the DILabel metadata. Theintrinsic will follow the label immediately. Backend could get thelabel metadata through the intrinsic's parameter.We also create DIBuilder API for labels to be used by Frontend.Frontend could use createLabel() to allocate DILabel objects, and useinsertLabel() to insert llvm.dbg.label intrinsic in LLVM IR.Differential Revision: https://reviews.llvm.org/D45024Patch by Hsiangkai Wang.llvm-svn: 331841 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 09 May 2018 02:40:45 +0000 Shiva Chen <shiva0217@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#ee88ed67 [DWARF] Fix incorrect prologue end line record.The prologue-end line record must be emitted after the lastinstruction that is part of the function frame setup code and beforethe instruction that marks the beginning of the function body.Patch by Carlos Alberto Enciso!Differential Revision: https://reviews.llvm.org/D41762llvm-svn: 325143 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 14 Feb 2018 17:35:52 +0000 Paul Robinson <paul.robinson@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#1e68724d Remove alignment argument from memcpy/memmove/memset in favour of alignment attributes (Step 1)Summary: This is a resurrection of work first proposed and discussed in Aug 2015: http://lists.llvm.org/pipermail/llvm-dev/2015-August/089384.htmland initially landed (but then backed out) in Nov 2015: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20151109/312083.html The @llvm.memcpy/memmove/memset intrinsics currently have an explicit argumentwhich is required to be a constant integer. It represents the alignment of thedest (and source), and so must be the minimum of the actual alignment of thetwo. This change is the first in a series that allows source and dest to eachhave their own alignments by using the alignment attribute on their arguments. In this change we:1) Remove the alignment argument.2) Add alignment attributes to the source & dest arguments. We, temporarily, require that the alignments for source & dest be equal. For example, code which used to read: call void @llvm.memcpy.p0i8.p0i8.i32(i8* %dest, i8* %src, i32 100, i32 4, i1 false)will now read call void @llvm.memcpy.p0i8.p0i8.i32(i8* align 4 %dest, i8* align 4 %src, i32 100, i1 false) Downstream users may have to update their lit tests that check for@llvm.memcpy/memmove/memset call/declaration patterns. The following extended sed scriptmay help with updating the majority of your tests, but it does not catch all possiblepatterns so some manual checking and updating will be required.s~declare void @llvm\.mem(set|cpy|move)\.p([^(]*)\((.*), i32, i1\)~declare void @llvm.mem\1.p\2(\3, i1)~gs~call void @llvm\.memset\.p([^(]*)i8\(i8([^*]*)\* (.*), i8 (.*), i8 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.memset.p\1i8(i8\2* \3, i8 \4, i8 \5, i1 \6)~gs~call void @llvm\.memset\.p([^(]*)i16\(i8([^*]*)\* (.*), i8 (.*), i16 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.memset.p\1i16(i8\2* \3, i8 \4, i16 \5, i1 \6)~gs~call void @llvm\.memset\.p([^(]*)i32\(i8([^*]*)\* (.*), i8 (.*), i32 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.memset.p\1i32(i8\2* \3, i8 \4, i32 \5, i1 \6)~gs~call void @llvm\.memset\.p([^(]*)i64\(i8([^*]*)\* (.*), i8 (.*), i64 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.memset.p\1i64(i8\2* \3, i8 \4, i64 \5, i1 \6)~gs~call void @llvm\.memset\.p([^(]*)i128\(i8([^*]*)\* (.*), i8 (.*), i128 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.memset.p\1i128(i8\2* \3, i8 \4, i128 \5, i1 \6)~gs~call void @llvm\.memset\.p([^(]*)i8\(i8([^*]*)\* (.*), i8 (.*), i8 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.memset.p\1i8(i8\2* align \6 \3, i8 \4, i8 \5, i1 \7)~gs~call void @llvm\.memset\.p([^(]*)i16\(i8([^*]*)\* (.*), i8 (.*), i16 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.memset.p\1i16(i8\2* align \6 \3, i8 \4, i16 \5, i1 \7)~gs~call void @llvm\.memset\.p([^(]*)i32\(i8([^*]*)\* (.*), i8 (.*), i32 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.memset.p\1i32(i8\2* align \6 \3, i8 \4, i32 \5, i1 \7)~gs~call void @llvm\.memset\.p([^(]*)i64\(i8([^*]*)\* (.*), i8 (.*), i64 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.memset.p\1i64(i8\2* align \6 \3, i8 \4, i64 \5, i1 \7)~gs~call void @llvm\.memset\.p([^(]*)i128\(i8([^*]*)\* (.*), i8 (.*), i128 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.memset.p\1i128(i8\2* align \6 \3, i8 \4, i128 \5, i1 \7)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i8\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i8 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.mem\1.p\2i8(i8\3* \4, i8\5* \6, i8 \7, i1 \8)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i16\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i16 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.mem\1.p\2i16(i8\3* \4, i8\5* \6, i16 \7, i1 \8)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i32\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i32 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.mem\1.p\2i32(i8\3* \4, i8\5* \6, i32 \7, i1 \8)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i64\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i64 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.mem\1.p\2i64(i8\3* \4, i8\5* \6, i64 \7, i1 \8)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i128\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i128 (.*), i32 [01], i1 ([^)]*)\)~call void @llvm.mem\1.p\2i128(i8\3* \4, i8\5* \6, i128 \7, i1 \8)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i8\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i8 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.mem\1.p\2i8(i8\3* align \8 \4, i8\5* align \8 \6, i8 \7, i1 \9)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i16\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i16 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.mem\1.p\2i16(i8\3* align \8 \4, i8\5* align \8 \6, i16 \7, i1 \9)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i32\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i32 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.mem\1.p\2i32(i8\3* align \8 \4, i8\5* align \8 \6, i32 \7, i1 \9)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i64\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i64 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.mem\1.p\2i64(i8\3* align \8 \4, i8\5* align \8 \6, i64 \7, i1 \9)~gs~call void @llvm\.mem(cpy|move)\.p([^(]*)i128\(i8([^*]*)\* (.*), i8([^*]*)\* (.*), i128 (.*), i32 ([0-9]*), i1 ([^)]*)\)~call void @llvm.mem\1.p\2i128(i8\3* align \8 \4, i8\5* align \8 \6, i128 \7, i1 \9)~g The remaining changes in the series will:Step 2) Expand the IRBuilder API to allow creation of memcpy/memmove with differing source and dest alignments.Step 3) Update Clang to use the new IRBuilder API.Step 4) Update Polly to use the new IRBuilder API.Step 5) Update LLVM passes that create memcpy/memmove calls to use the new IRBuilder API, and those that use use MemIntrinsicInst::[get|set]Alignment() to use getDestAlignment() and getSourceAlignment() instead.Step 6) Remove the single-alignment IRBuilder API for memcpy/memmove, and the MemIntrinsicInst::[get|set]Alignment() methods.Reviewers: pete, hfinkel, lhames, reames, bolluReviewed By: reamesSubscribers: niosHD, reames, jholewinski, qcolombet, jfb, sanjoy, arsenm, dschuff, dylanmckay, mehdi_amini, sdardis, nemanjai, david2050, nhaehnle, javed.absar, sbc100, jgravelle-google, eraman, aheejin, kbarton, JDevlieghere, asb, rbar, johnrusso, simoncook, jordy.potman.lists, apazos, sabuasal, llvm-commitsDifferential Revision: https://reviews.llvm.org/D41675llvm-svn: 322965 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Fri, 19 Jan 2018 17:13:12 +0000 Daniel Neilson <dneilson@azul.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#ea89ff7c CodeView symbol dumper: use symbolic names for registershttps://reviews.llvm.org/D38469llvm-svn: 314690 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Mon, 02 Oct 2017 17:44:47 +0000 Hans Wennborg <hans@hanshq.net> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#8d8888ff [codeview] Change readobj symbol dumping formatAvoid duplicating DictScope with hand-written names everywhere. Printthe S_-prefixed symbol kind for every record. This should make it easierto search for certain kinds of records when debugging PDB linking.llvm-svn: 307732 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 11 Jul 2017 23:41:41 +0000 Reid Kleckner <rnk@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#c64acfd4 Emit S_COMPILE3 CodeView recordCodeView has an S_COMPILE3 record to identify the compiler and source language of the compiland. This record comes first in the debug$S section for the compiland. The debuggers rely on this record to know the source language of the code.There was a little test fallout from introducing a new record into the symbols subsection.Differential Revision: https://reviews.llvm.org/D24317llvm-svn: 281990 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Tue, 20 Sep 2016 17:20:51 +0000 Adrian McCarthy <amccarth@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll#f3c3c132 Generate codeview for array type metadata.Differential Revision: http://reviews.llvm.org/D21107llvm-svn: 272187 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-array.ll Wed, 08 Jun 2016 18:22:59 +0000 Adrian McCarthy <amccarth@google.com>