llvm dev - Jan 2020 - Where does LLVM/Clang resolves duplicate block labels?

Hello,
I’m trying to find where Clang/LLVM resolves duplicate block labels when the
code is being generated (from C to LLVM IR) and the only place I can see where
this will happen is in ValueSymbolTable’s makeUniqueName function. After tracing
through, I realized that block label names (like if.then and if.else) don’t go
through that process to check if the label name already exists. But after
emitting the .ll file, those labels have a number attached to make each instance
unique. Now I’m wondering where those naming conflicts for block labels are
being resolved?

— Kaarthik A.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200116/7c9a0eb3/attachment.html>

IRBuilder probably just gives them unique names even though you ask for a
name that's a duplicate.

On Thu, Jan 16, 2020 at 2:43 PM Kaarthik Alagapan via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello,
> I’m trying to find where Clang/LLVM resolves duplicate block labels when
> the code is being generated (from C to LLVM IR) and the only place I can
> see where this will happen is in ValueSymbolTable’s makeUniqueName
> function. After tracing through, I realized that block label names (like
> if.then and if.else) don’t go through that process to check if the label
> name already exists. But after emitting the .ll file, those labels have a
> number attached to make each instance unique. Now I’m wondering where those
> naming conflicts for block labels are being resolved?
>
> — Kaarthik A.
> _______________________________________________
> 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/20200116/9a69de89/attachment.html>