bcm5719-llvm/llvm/test/Linker, branch meklort-10.0.1

Linker/module-max-warn.ll: Fix test to be compatible with Windows file separators

2020-02-13T10:37:18+00:00

(cherry picked from commit 84eeee65804ba070c50978be1c741a1756779079)

IR Linking: Support merging Warning+Max module metadata flags

2020-02-11T09:36:46+00:00

Summary: Debug Info Version was changed to use "Max" instead of "Warning" per the original design intent - but this maxes old/new IR unlinkable, since mismatched merge styles are a linking failure. It seems possible/maybe reasonable to actually support the combination of these two flags: Warn, but then use the maximum value rather than the first value/earlier module's value. Reviewers: tejohnson Differential Revision: https://reviews.llvm.org/D74257 (cherry picked from commit ba9cae58bbdd41451ee67773c9d0f90a01756f12)

Migrate function attribute "no-frame-pointer-elim"="false" to "frame-pointer"="none" as cleanups after D56351

2019-12-25T00:27:51+00:00

Migrate function attribute "no-frame-pointer-elim" to "frame-pointer"="all" as cleanups after D56351

2019-12-24T23:57:33+00:00

[IRMover] Set Address Space for moved global values

2019-11-06T00:32:48+00:00

Summary: Set Address Space when creating a new function (from another). Fix PR41154. Patch by Ehud Katz Reviewers: tejohnson, chandlerc Reviewed By: tejohnson Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D69361

Remove some unnecessary REQUIRES: shell lines

2019-09-10T00:06:52+00:00

This means these tests will run on Windows. Replace one with UNSUPPORTED: system-windows. llvm-svn: 371473

IR: print value numbers for unnamed function arguments

2019-08-03T14:28:34+00:00

For consistency with normal instructions and clarity when reading IR, it's best to print the %0, %1, ... names of function arguments in definitions. Also modifies the parser to accept IR in that form for obvious reasons. llvm-svn: 367755

IR: Teach GlobalIndirectSymbol::getBaseObject() to handle more kinds of expressions.

2019-07-24T22:23:05+00:00

For aliases, any expression that lowers at the MC level to global_object or global_object+constant is valid at the object file level. getBaseObject() should return a result if the aliasee ends up being of that form even if the IR used to produce it is somewhat unconventional. Note that this is different from what stripInBoundsOffsets() and that family of functions is doing. Those functions are concerned about semantic properties of IR, whereas here we only care about the lowering result. Therefore reimplement getBaseObject() in a way that matches the lowering result. This fixes a crash when producing a summary for aliases such as that in the included test case. Differential Revision: https://reviews.llvm.org/D65115 llvm-svn: 366952

Reapply: IR: add optional type to 'byval' function parameters

2019-05-30T18:48:23+00:00

When we switch to opaque pointer types we will need some way to describe how many bytes a 'byval' parameter should occupy on the stack. This adds a (for now) optional extra type parameter. If present, the type must match the pointee type of the argument. The original commit did not remap byval types when linking modules, which broke LTO. This version fixes that. Note to front-end maintainers: if this causes test failures, it's probably because the "byval" attribute is printed after attributes without any parameter after this change. llvm-svn: 362128

[IRMover] Improve diagnostic messages for conflicting metadata

2019-05-16T05:23:13+00:00

This does the similar for error messages as rL344011 has done for warnings. With llvm::lto::LTO, the error might appear when LTO::run() is executed. In that case, the calling code cannot know which module causes the error and, subsequently, cannot hint the user. Differential Revision: https://reviews.llvm.org/D61880 llvm-svn: 360857