llvm-project.git/llvm/test/CodeGen/AVR/sections.ll, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [CodeGen] Clean up tests that depend on implicit .text in MCAsmStreamer 2024-12-23T05:11:32+00:00 Fangrui Song i@maskray.me 2024-12-23T05:11:32+00:00 5712e293fb317b50166766ba86b969eb13fcd069 






[test] Change llc -march= to -mtriple=
2023-09-11T21:42:37+00:00

Fangrui Song
i@maskray.me

2023-09-11T21:42:37+00:00

806761a7629df268c8aed49657aeccffa6bca449

The issue is uncovered by #47698: for IR files without a target triple,
-mtriple= specifies the full target triple while -march= 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, -march= is error-prone and not recommended for tests without a target
triple. The issue has been benign as we recognize $unknown-apple-darwin as ELF instead
of rejecting it outrightly.





The issue is uncovered by #47698: for IR files without a target triple,
-mtriple= specifies the full target triple while -march= 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, -march= is error-prone and not recommended for tests without a target
triple. The issue has been benign as we recognize $unknown-apple-darwin as ELF instead
of rejecting it outrightly.







[AVR][MC] Generate section '.progmemX.data' for extended flash banks
2022-01-20T02:53:10+00:00

Ben Shi
ben.shi@streamcomputing.com

2021-12-18T10:03:11+00:00

c1dd607463dbaa0398df1c88b6759dde03be6353

Reviewed By: aykevl

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





Reviewed By: aykevl

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







[AVR] Do not place functions in .progmem.data
2020-04-20T11:56:38+00:00

Ayke van Laethem
aykevanlaethem@gmail.com

2020-04-15T15:30:47+00:00

8aad119d93e3cc399012f1379e705b06f38def3d

Previously, the AVR backend would put functions in .progmem.data. This
is probably a regression from when functions still lived in address
space 0. With this change, only global constants are placed in
.progmem.data.

This is not complete: avr-gcc additionally respects -fdata-sections for
progmem global constants, which LLVM doesn't yet do. But fixing that is
a bit more complicated (and I believe other backends such as RISC-V
might also have similar issues).

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





Previously, the AVR backend would put functions in .progmem.data. This
is probably a regression from when functions still lived in address
space 0. With this change, only global constants are placed in
.progmem.data.

This is not complete: avr-gcc additionally respects -fdata-sections for
progmem global constants, which LLVM doesn't yet do. But fixing that is
a bit more complicated (and I believe other backends such as RISC-V
might also have similar issues).

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