Open llvmbot opened 3 years ago
I am able to reproduce this on clang++-trunk. Should this be marked as confirmed?
$ /home/cnsun/usr/bin/clang++-trunk -v
clang version 14.0.0 (https://github.com/llvm/llvm-project.git 73cfa982ba6380ee96c017d044f3f580eb8e18bd)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/cnsun/usr/bin
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/10
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/9
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/10
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
I am able to reproduce this on clang++-trunk. Should this be marked as confirmed?
Sure.
Extended Description
How to produce:
$ clang++ -S -emit-llvm re.cpp -o dbg.ll -g $ clang++ -S -emit-llvm re.cpp -o rel.ll
Then diff the content of dbgl.ll and rel.ll
Found that the ctor of Re3 (_ZN6extend3re33Re3C2Ev) precedes before the another funciton in rel.ll file, but the order changes in dbg.ll