Revision c27223607daaeee94ae477a1fdeab9b8784c9a8d authored by Keno Fischer on 14 July 2023, 21:07:02 UTC, committed by Keno Fischer on 14 July 2023, 21:09:24 UTC
Fixes the case from #50518, but we actually have two test cases in the tests that also hit this (e.g. this one: ``` f40964(xs::Int...=1; k = 2) = (xs, k) ```), but just happened not to hit the bad codegen path. #50556, once merged would have complained on those definitions as well, without this fix.
1 parent ae08077
llvm.version
# -*- makefile -*-
## jll artifact
LLVM_JLL_NAME := libLLVM
LLVM_ASSERT_JLL_VER := 15.0.7+5
## source build
# Version number of LLVM
LLVM_VER := 15.0.7
# Git branch name in `LLVM_GIT_URL` repository
LLVM_BRANCH=julia-15.0.7-5
# Git ref in `LLVM_GIT_URL` repository
LLVM_SHA1=julia-15.0.7-5
## Following options are used to automatically fetch patchset from Julia's fork. This is
## useful if you want to build an external LLVM while still applying Julia's patches.
# Set to 1 if you want to automatically apply Julia's patches to a different fork of LLVM.
LLVM_APPLY_JULIA_PATCHES := 0
# GitHub repository to use for fetching the Julia patches to apply to LLVM source code.
LLVM_JULIA_DIFF_GITHUB_REPO := https://github.com/llvm/llvm-project
# Base GitHub ref for generating the diff.
LLVM_BASE_REF := llvm:llvmorg-15.0.7
# Julia fork's GitHub ref for generating the diff.
LLVM_JULIA_REF := JuliaLang:julia-15.0.7-5
Computing file changes ...
