Skip to content

LTO not working #12

@jansol

Description

@jansol

When compiling with -flto, the build fails with

/tmp/ccxd5DLE.s: Assembler messages:
/tmp/ccxd5DLE.s:8773: Error: unrecognized opcode `lwu s1,.LANCHOR0+371'
/tmp/ccxd5DLE.s:15496: Error: unrecognized opcode `lwu a4,.LANCHOR5+476'
/tmp/ccxd5DLE.s:15950: Error: unrecognized opcode `lwu a5,.LANCHOR5+552'
/tmp/ccxd5DLE.s:16031: Error: unrecognized opcode `lwu a1,.LANCHOR5+476'
/tmp/ccxd5DLE.s:16136: Error: unrecognized opcode `lwu a5,.LANCHOR5+568'
/tmp/ccxd5DLE.s:16183: Error: unrecognized opcode `lwu a5,.LANCHOR5+568'
/tmp/ccxd5DLE.s:16184: Error: unrecognized opcode `lwu a4,.LANCHOR5+1604'
/tmp/ccxd5DLE.s:16199: Error: unrecognized opcode `lwu a5,.LANCHOR5+568'
/tmp/ccxd5DLE.s:16227: Error: unrecognized opcode `lwu a5,.LANCHOR5+1604'
lto-wrapper: fatal error: riscv32-unknown-elf-gcc returned 1 exit status

Which is interesting because lwu is AFAIK only a legal opcode in rv64 and I'm definitely compiling everything with -march=rv32imcxgap8. I wonder if it has to do with the libgcc.a build in this repo? Since that is the only precompiled binary involved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions