[llvm-dev] Initialize isel bug - amdgpu

[Hendrik Greving via llvm-dev]

Right not a major bug, besides that it also affects debug_type for
debug-only, print-after etc. e.g. it might be an issue for scripts.

On Wed, May 12, 2021 at 10:27 AM Nemanja Ivanovic <nemanja.i.ibm at gmail.com>
wrote:

> Yeah, it shows up in the print-after... for all targets :)
>
> # *** IR Dump After PowerPC DAG->DAG Pattern Instruction Selection
> (amdgpu-isel) ***:
>
> I've always found it to be a slight nuisance but didn't look into fixing
> it since it has no effect on normal use of the compiler.
>
> On Wed, May 12, 2021 at 12:55 PM Hendrik Greving via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Did you guys notice that because AMDGPU is the only upstream target
>> calling initializeAMDGPUDAGToDAGISelPass(), llvm::SelectionDAGISel::ID is
>> always registered for this pass, so you have to -print-after=amdgpu-isel,
>> even on x86.
>>
>> Is there a bug for this?
>> _______________________________________________
>> 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/20210512/ea792dc2/attachment.html>