![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
TMI: Slowness
May. 22nd, 2013 08:07 pmA frustrating day. On the plus side, I did solve yesterday's problem with the duplicate __test identifier. It turned out I was calling the driver functions wrong and it was literally synthesizing a test module twice. I was able to fix that bug.
Once I fixed that, I got this horrible resolve error:
The error refers to the code for intrinsics (primops, basically) that rustc injects everywhere. It's complaining that bool is a function but is being used like a type. But... bool is a type! A primitive one, at that. I'd expect this to happen if there was a function somewhere called bool (maybe), but there isn't.
This was when I was trying to use rustpkg to build a test module. So next I decided to just compile a regular main module. So then I got:
as an ICE in trans.
Given that all of this just comes from changing search paths so rustpkg can find libstd and not treat it as a remote-package-to-download, I'm... flummoxed.
Also, rustc as a whole seemed to get a lot slower sometime in the past two days. As in, even running three builds in different workspaces, at the same time, resulted in a longer than usual wait for any one of them to complete. And I wasn't running out of physical RAM.
Because of that, I spent some time while waiting for compiles to finish nominating bugs. I sorted github issues by least-recently-commented-on. As a result, all the open issues have been touched sometime in the past 2 months, and there are now 142 nominated bugs. I... don't think we'll get through all of them in the triage meeting tomorrow.
Once I fixed that, I got this horrible resolve error:
<intrinsic>:58:37: 58:41 error: found value name used as a type: def_fn({crate: 1, node: 160381}, impure_fn)
<intrinsic>:58 fn visit_estr_uniq(&self) -> bool;
The error refers to the code for intrinsics (primops, basically) that rustc injects everywhere. It's complaining that bool is a function but is being used like a type. But... bool is a type! A primitive one, at that. I'd expect this to happen if there was a function somewhere called bool (maybe), but there isn't.
This was when I was trying to use rustpkg to build a test module. So next I decided to just compile a regular main module. So then I got:
rust: task failed at 'ty_fn_ret() called on non-fn type: &ty_nil', /Users/tjc/rust2/src/librustc/middle/ty.rs:2822
as an ICE in trans.
Given that all of this just comes from changing search paths so rustpkg can find libstd and not treat it as a remote-package-to-download, I'm... flummoxed.
Also, rustc as a whole seemed to get a lot slower sometime in the past two days. As in, even running three builds in different workspaces, at the same time, resulted in a longer than usual wait for any one of them to complete. And I wasn't running out of physical RAM.
Because of that, I spent some time while waiting for compiles to finish nominating bugs. I sorted github issues by least-recently-commented-on. As a result, all the open issues have been touched sometime in the past 2 months, and there are now 142 nominated bugs. I... don't think we'll get through all of them in the triage meeting tomorrow.