[Mlir-commits] [mlir] [mlir][linalg] Extend `FuseElementwiseOps` pattern to work with named ops (PR #144922)

Renato Golin llvmlistbot at llvm.org
Sat Nov 8 10:15:27 PST 2025


rengolin wrote:

> > That's not a reasonable upstream path. You can ask people to help you, and they can agree to help you, but ultimately, your downstream cost must be paid by your team. Other downstream projects already pay their own costs, and it's unreasonable to ask them to pay yours, too. This is a key assumption of the whole LLVM project since its inception and I don't see it changing now.
> 
> I think you may be missing the point. I help people in this community, at this point without it being part of my job, and expect nothing in return. Most of the time, these people help me in return eventually, often without me asking. This is the community I'd like to be in. If everybody is only there for their own self-interest, I suspect we get endless irreconcilable arguing over minor details.

I'm struggling to see how you got there from what I said. This is not about self-interest, it's about upstream vs. downstream. It's about being selfless upstream, not selfish downstream.

We should all design and discuss upstream LLVM together, and consider the downstream users in that design, but not ask other people to pay your downstream costs, because we all have our own. 

In a nutshell, we all pay the upstream cost together, and we all pay our own downstream cost alone. Let's design an upstream compiler infrastructure, but not at the cost of making it solely a downstream scaffolding.

https://github.com/llvm/llvm-project/pull/144922


More information about the Mlir-commits mailing list