[llvm-dev] Moving the AVR backend out of experimental (original) (raw)
Dylan McKay via llvm-dev llvm-dev at lists.llvm.org
Mon Feb 24 21:27:03 PST 2020
- Previous message: [llvm-dev] Moving the AVR backend out of experimental
- Next message: [llvm-dev] RFC Storing BB order in llvm::Instruction for faster local dominance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Would that be fixed with this patch? It makes llvm-objdump work for me and allows debugging with avr-gdb.
Can you perhaps point me to the tests that are failing?
I re-ran the test suite with '-DLLVM_TARGET_ARCH=avr-unknown-unknown' and now the only errors I get are JIT errors related to no JIT compiler enabled for my host machine, x86. It seems the few failing generic CodeGen tests have since been fixed, along with the ~80 or so DebugInfo tests no doubt fixed by one of Ayke's recent changes.
I've also opened up a patch to make AVR an official backend: https://reviews.llvm.org/D75099. All comments welcome.
Let's move the discussion there.
- Dylan
On Wed, Feb 19, 2020 at 5:05 AM Matt Arsenault <arsenm2 at gmail.com> wrote:
On Feb 18, 2020, at 02:44, Dylan McKay via llvm-dev <_ _llvm-dev at lists.llvm.org> wrote: Fixing of the DebugInfo tests would make the AVR official backend pitch much more tenable. I don’t see why this would be a blocker. It’s not like everything is perfectly functional on all targets -Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200225/5c4cbe64/attachment.html>
- Previous message: [llvm-dev] Moving the AVR backend out of experimental
- Next message: [llvm-dev] RFC Storing BB order in llvm::Instruction for faster local dominance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]