-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal compiler error in trans, with bind and iterators #2185
Comments
I took the liberty of giving the bug a slightly more descriptive title, since rustc often dumps core after an internal compiler error. |
I minimized the test case a tiny bit: https://gist.github.com/2466203 I'm seeing some behavior in Anyway, @marijnh said he would look at this further. |
…ust-lang#2185) Changed how `kani-driver` passess arguments to `kani-compiler`. We now have one option, `--kani-compiler`, that changes how we configure rustc, and all the other Kani specific arguments are added to `-C llvm-args`. We no longer need to keep the arguments in a certain order or need to use KANI_FLAGS environment variable. In the `kani-compiler` we no longer parse the arguments before invoking rustc, we initially detect whether users want to use the Kani flavour of the compiler by looking for a `--kani-compiler` flag. If `--kani-compiler` flag is found, we configure rustc's driver to use our custom backend and our custom callback. We then invoke the driver with the command line arguments excluding the `--kani-compiler` flag. During the callback configuration we initialize the Kani specific flags that are passed via `-C llvm-args`. If there isn't any `--kani-compiler` flag, we just invoke rustc with all the given arguments. Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com>
Compiling following source, rustc dumps core with error messages.
The text was updated successfully, but these errors were encountered: