llvm-project.git/llvm/test/Object/AMDGPU/objdump.s, branch users/nico/python-2

[test] Change llvm-mc -arch= to -triple=

2023-09-11T21:51:50+00:00

The issue is uncovered by #47698: for assembly files, -triple= specifies the
full target triple while -arch= merely sets the architecture part of the default
target triple, leaving a target triple which may not make sense, e.g.
riscv64-apple-darwin.

Therefore, -arch= is error-prone and not recommended for tests. The issue has
been benign as we recognize $unknown-apple-darwin as ELF instead of rejecting it
outrightly.

Due to the nature of the issue, we don't see the issue in tests using
architectures that any of Mach-O/COFF/XCOFF supports.

AMDGPU: Update AMDHSA code object version handling

2020-10-14T17:04:27+00:00

Differential Revision: https://reviews.llvm.org/D89076

[test] llvm/test/: change llvm-objdump single-dash long options to double-dash options

2020-03-16T00:46:23+00:00

As announced here: http://lists.llvm.org/pipermail/llvm-dev/2019-April/131786.html

Grouped option syntax (POSIX Utility Conventions) does not play well with -long-option
A subsequent change will reject -long-option.

[llvm-objdump] -d: print `00000000 :` instead of `00000000 foo:`

2020-03-06T02:05:28+00:00

The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier.

`.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive.
Without `-LABEL`, the CHECK line can match the `Disassembly of section`
line and causes the next `CHECK-NEXT:` to fail.

```
Disassembly of section .foo:

0000000000001634 .foo:
```

Bdragon: <> has metalinguistic connotation. it just "feels right"

Reviewed By: rupprecht

Differential Revision: https://reviews.llvm.org/D75713

[llvm-objdump] Print file format in lowercase to match GNU output.

2020-02-12T16:17:01+00:00

Summary:
GNU objdump prints the file format in lowercase, e.g. `elf64-x86-64`. llvm-objdump prints `ELF64-x86-64` right now, even though piping that into llvm-objcopy refuses that as a valid arch to use.

As an example of a problem this causes, see: https://github.com/ClangBuiltLinux/linux/issues/779

Reviewers: MaskRay, jhenderson, alexshap

Reviewed By: MaskRay

Subscribers: tpimh, sbc100, grimar, jvesely, nhaehnle, kerbowa, cfe-commits, llvm-commits

Tags: #clang, #llvm

Differential Revision: https://reviews.llvm.org/D74433

AMDGPU: Enable code object v3 for AMDHSA only

2018-11-15T02:32:43+00:00

Differential Revision: https://reviews.llvm.org/D54186

llvm-svn: 346923

Revert r345542: AMDGPU: Enable code object v3 by default

2018-10-30T22:02:40+00:00

It breaks mesa.

llvm-svn: 345662

AMDGPU: Enable code object v3 by default

2018-10-29T21:07:27+00:00

Differential Revision: https://reviews.llvm.org/D53525

llvm-svn: 345542

[AMDGPU][MC][GFX8][GFX9] Corrected names of integer v_{add/addc/sub/subrev/subb/subbrev}

2017-11-20T18:24:21+00:00

See bug 34765: https://bugs.llvm.org//show_bug.cgi?id=34765

Reviewers: tamazov, SamWot, arsenm, vpykhtin

Differential Revision: https://reviews.llvm.org/D40088

llvm-svn: 318675

AMDGPU: Add ELFOSABI_AMDGPU_PAL

2017-10-03T20:54:07+00:00

llvm-svn: 314843