Wrong mode for main() argument causes LLVM assertion failure #3528

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Closed

catamorphism opened this issue Sep 18, 2012 · 1 comment

Labels

A-type-system I-ICE

Milestone

Contributor

catamorphism commented Sep 18, 2012

fn main(+_args: ~[~str]) {}

results in:

Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Args[i]->getType()) && "Calling a function with a bad signature!"), function init, file /Users/tchevalier/rust/src/llvm/lib/VMCore/Instructions.cpp, line 280.

I know modes are going away, but in general it's probably worth testing that doing various weird things to main's signature yields a proper error.

The text was updated successfully, but these errors were encountered:

Contributor Author

catamorphism commented Dec 7, 2012

Meh, modes are gone and I am unmotivated to add more tests for this at the moment :-)

catamorphism closed this as completed

RalfJung pushed a commit to RalfJung/rust that referenced this issue


          Auto merge of rust-lang#3536 - tiif:add_rustbot_feat, r=RalfJung

3c6d194

Add rustbot claim feature

Add rustbot ``claim``, ``release-assignment`` and ``assign-user`` as mentioned in rust-lang#3528.

rustbot issue assignment documentation: https://forge.rust-lang.org/triagebot/issue-assignment.html
pr trigger option documentation: https://forge.rust-lang.org/triagebot/pr-assignment.html#additional-new-pr-trigger-options

# for free to join this conversation on GitHub. Already have an account? # to comment