Skip to content

Conversation

xlauko
Copy link
Collaborator

@xlauko xlauko commented Feb 26, 2025

This uses the assembly format for the optional return type and keeps a custom printer/parser only for function parameters, which still require a custom form for ellipses.

@bcardosolopes
Copy link
Member

(cc @dkolsen-pgi)

@xlauko xlauko merged commit c35a706 into llvm:main Feb 26, 2025
6 checks passed
@xlauko xlauko deleted the xlauko/function-type-format branch February 26, 2025 23:00
dkolsen-pgi added a commit to dkolsen-pgi/llvm-project that referenced this pull request Feb 26, 2025
Incorporate llvm/clangir#1413 to simplify the
parsing/printing of `FuncType`.

Get rid of `FuncOp::verifyType` which did nothing useful.
xlauko added a commit to xlauko/clangir that referenced this pull request Feb 28, 2025
This uses the assembly format for the optional return type and keeps a
custom printer/parser only for function parameters, which still require
a custom form for ellipses.
xlauko added a commit to xlauko/clangir that referenced this pull request Feb 28, 2025
This uses the assembly format for the optional return type and keeps a
custom printer/parser only for function parameters, which still require
a custom form for ellipses.
lanza pushed a commit that referenced this pull request Mar 18, 2025
This uses the assembly format for the optional return type and keeps a
custom printer/parser only for function parameters, which still require
a custom form for ellipses.
terapines-osc-cir pushed a commit to Terapines/clangir that referenced this pull request Sep 2, 2025
This uses the assembly format for the optional return type and keeps a
custom printer/parser only for function parameters, which still require
a custom form for ellipses.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants