llvm dev - Oct 2021 - Question about -flto behavior

Hi All,

When -flto is combined with -S on the clang command line, the output .s file
contains IR content instead of target assembly language.

Is this expected/correct behavior? I was anticipating that the output .s file
would contain target assembly code.

~ Todd Snider
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211018/3191b445/attachment.html>

Yeah, sounds expected to me - flto produces object files that aren't really
object files - instead they're LLVM IR (bitcode) that the linker
identifies, then calls back into LLVM to link the IR, optimize on that IR,
then produce object code/assembly/whatever).

So the "assembly" form of an "object" (really LLVM bitcode)
file is LLVM
textual IR.

On Mon, Oct 18, 2021 at 1:56 PM Snider, Todd via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi All,
>
>
>
> When -flto is combined with -S on the clang command line, the output .s
> file contains IR content instead of target assembly language.
>
>
>
> Is this expected/correct behavior? I was anticipating that the output .s
> file would contain target assembly code.
>
>
>
> ~ Todd Snider
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211018/3aca9c2b/attachment.html>