-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Codegen: Query span as late as possible #78280
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
if let Some(g) = self.get_declared_value(sym) { | ||
if self.val_ty(g) != self.type_ptr_to(llty) { | ||
span_bug!(span, "Conflicting types for static"); | ||
span_bug!(self.tcx.def_span(def_id), "Conflicting types for static"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a reason you aren't using the Item
span here? That seems easier to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the moment, it is, yes. Consider this change a step towards #43088 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I actually dont know, by the way, if these are identical, so it's kind of a "let's see what the tests think" kind of change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the tests won't think anything here will they? This is a span_bug
so we should never reach this in tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub needs a reaction that indicates how blind I can be :)
r? @lcnr @bors try @rust-timer queue |
Awaiting bors try build completion |
@bors try |
⌛ Trying commit ee0e694620a854aa79120797a51828808e09520a with merge ecfe4ae31e98013262cabb9089048076a74d3864... |
💔 Test failed - checks-actions |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Hmm, can I? |
@bugadani: 🔑 Insufficient privileges: not in try users |
@bors try |
⌛ Trying commit c1b9d05991920c2b795c40ddb4afa030a760dbd0 with merge 3de59e1f390995a45756def4e7e157930d184b00... |
☀️ Try build successful - checks-actions |
Queued 3de59e1f390995a45756def4e7e157930d184b00 with parent 7bade6e, future comparison URL. |
Finished benchmarking try commit (3de59e1f390995a45756def4e7e157930d184b00): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
completely forgot about this PR, sry. Afaict perf was slightly positive and it seems good to land, so @bors r+ |
📌 Commit caf9131 has been approved by |
@bors retry |
⌛ Testing commit caf9131 with merge 53cc9ffee1ce28774351e040ee9338d677cc2ec7... |
💔 Test failed - checks-actions |
@pietroalbini could you please retry this again? The previous one looks like it failed with a network error:
|
@bors retry |
⌛ Testing commit caf9131 with merge 2f73a3e543c922ffcd80efb5375b9b711af47bb7... |
💔 Test failed - checks-actions |
I'm starting to think this PR is cursed :( |
@bors retry |
☀️ Test successful - checks-actions |
No description provided.