Skip to content

documentation: Add bibtex + publications to README#5586

Open
AntonLydike wants to merge 2 commits intomainfrom
anton/add-publications
Open

documentation: Add bibtex + publications to README#5586
AntonLydike wants to merge 2 commits intomainfrom
anton/add-publications

Conversation

@AntonLydike
Copy link
Collaborator

First attempt at finding a place to have all the work using xDSL in one place for easy lookup.

Open for any feedback!

@AntonLydike AntonLydike self-assigned this Jan 26, 2026
@AntonLydike AntonLydike added the documentation Documentation label Jan 26, 2026
@AntonLydike
Copy link
Collaborator Author

The order of the publications is "order of discovery by me" at the moment, but should probably be revised into something more useful.

Also, I'm not 100% sure all papers actually use xDSL internally, and/or if I missed any (probably).

urldate = {2026-01-26},
booktitle = {Proceedings of the 23rd {ACM}/{IEEE} {International} {Symposium} on {Code} {Generation} and {Optimization}},
publisher = {ACM},
author = {Fehr, Mathieu and Weber, Michel and Ulmann, Christian and Lopoukhine, Alexandre and Lücke, Martin Paul and Degioanni, Théo and Vasiladiotis, Christos and Steuwer, Michel and Grosser, Tobias},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that bibtex isn't very good at unicode, and things should be replaced by tex replacements

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is generated by Zotero and has worked for me so far. I know this is a weak argument. Open for suggestions, am not an expert on Tex (and specifically bibtex)

@codecov
Copy link

codecov bot commented Jan 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.14%. Comparing base (292a58a) to head (b42c770).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5586   +/-   ##
=======================================
  Coverage   86.14%   86.14%           
=======================================
  Files         392      392           
  Lines       56266    56266           
  Branches     6485     6485           
=======================================
  Hits        48472    48472           
  Misses       6262     6262           
  Partials     1532     1532           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

year = {2025},
pages = {179--192},
}
```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more thing: wouldn't this be a better fit for a specialised Citation.cff file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, didn't know this existed

Copy link
Collaborator Author

@AntonLydike AntonLydike Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those only work for @software or @dataset citations, not papers themselves

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +236 to +249
Other published works that use xDSL internally (feel free to open a PR to extend
this list):

- [Stencil-HMLS: A multi-layered approach to the automatic optimisation of stencil codes on FPGA](https://dl.acm.org/doi/abs/10.1145/3624062.3624543)
- [Fortran performance optimisation and auto-parallelisation by leveraging MLIR-based domain specific abstractions in Flang](https://dl.acm.org/doi/abs/10.1145/3624062.3624167)
- [A shared compilation stack for distributed-memory parallelism in stencil DSLs](https://dl.acm.org/doi/abs/10.1145/3620666.3651344)
- [A Multi-level Compiler Backend for Accelerated Micro-kernels Targeting RISC-V ISA Extensions](https://dl.acm.org/doi/abs/10.1145/3696443.3708952)
- [The Configuration Wall: Characterization and Elimination of Accelerator Configuration Overhead](https://dl.acm.org/doi/abs/10.1145/3760250.3762225)
- [First-Class Verification Dialects for MLIR](https://dl.acm.org/doi/abs/10.1145/3729309)
- [Integrating Quantum Software Tools with(in) MLIR](https://arxiv.org/abs/2601.02062)
- [eqsat: An Equality Saturation Dialect for Non-destructive Rewriting](https://arxiv.org/abs/2505.09363)
- [An MLIR pipeline for offloading Fortran to FPGAs via OpenMP](https://dl.acm.org/doi/full/10.1145/3731599.3767485)
- [Development of a Custom Compilation Workflow With MLIR Leveraging OpenFPM to Accelerate Particle Simulations](https://esim-project.eu/files/Images/people/chair-cc/theses/2508_Cornel_MA.pdf)
- [Quantum Oracle Synthesis from HDL Designs via Multi Level Intermediate Representation](https://re.public.polimi.it/handle/11311/1301614)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, but I wonder if it belongs somewhere in the docs instead? But also, maybe we could just link to this page?

https://scholar.google.com/scholar?cites=1122502081021143810&as_sdt=2005&sciodt=0,5&hl=en

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would personally say that having it on the README makes sense (especially if at the end).
Note that the google scholar page will show papers that cite xDSL but that don't use it, but also won't show the stencil paper that was published before xDSL?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think we should double-check these and then have them as a list of "Cool projects built using xDSL" or something along those lines. It's not the same as the citations on google

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, sounds good, let's have a manually curated list. I still think that it would be preferable in a doc page, as then we can have prettier formatting and maybe an abstract/links to repos? README space is relatively precious, and I think it's already overly long.

@tobiasgrosser
Copy link
Contributor

I feel the related work would work great at https://xdsl.dev/about/challenge/. We can make a page https://xdsl.dev/about/users? Also, these two pages need a proper rewrite. We should have a history page how xDSl started and then explain what it is today.

@superlopuh
Copy link
Member

Hi @AntonLydike, will you have time to iterate here in the next few days? Would love to minimise the number of open PRs, it's hard to keep track of all the things going on, and it feels like with the current suggestions resolved merging this is a no-brainer.

@AntonLydike
Copy link
Collaborator Author

Yeah, I will get this shipped later today I think!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants