sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for Wasm floating point instructions not in `core`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(wasm_numeric_instr)]`

This is a tracking issue for floating point instructions that aren't available in `core` but are available as simple instructions on Wasm directly.

### Public API

```rust
mod arch {
    mod wasm32 {
        pub fn f32_ceil(a: f32) -> f32;
        pub fn f32_floor(a: f32) -> f32;
        pub fn f32_trunc(a: f32) -> f32;
        pub fn f32_nearest(a: f32) -> f32;
        pub fn f32_sqrt(a: f32) -> f32;
        pub fn f64_ceil(a: f64) -> f64;
        pub fn f64_floor(a: f64) -> f64;
        pub fn f64_trunc(a: f64) -> f64;
        pub fn f64_nearest(a: f64) -> f64;
        pub fn f64_sqrt(a: f64) -> f64;
    }
}
```

### Steps / History

- [x] Implementation: https://github.com/rust-lang/stdarch/pull/1677
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

My impression from https://github.com/rust-lang/rust/issues/50145 was that these methods (except `sqrt()`) are not intended to ever be added to `core`. But looking at a [recent discussion in Zulip](https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/float.20methods.20in.20std.2C.20not.20core) it paints a different picture.

If indeed these methods are intended to come to `core`, then these additions will probably never be stabilized.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: react-native
Issue: UI issue in iOS with New Architecture in RN 0.75.3 — Unexpected padding behavior
Labels: Platform: iOS,Needs: Author Feedback,Needs: Repro,Newer Patch Available

### Description

I am facing an issue with the UI on iOS React Native 0.75.3 .UI elements are going out of their boundary and this behaviour does not occur on Android.

### Steps to reproduce

RN 0.75.3 (with new architecture) IOS .

### React Native Version

0.75.3

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.3.1
  CPU: (8) arm64 Apple M1
  Memory: 86.86 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v20.11.1/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2024.03.18.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.2 AI-232.10227.8.2321.11479570
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 3.3.1
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.3
    wanted: 0.75.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
It is not a crash .
```


### Reproducer

https://stackoverflow.com/questions/79166621/padding-issues-and-layout-breaking-in-production-ios-with-expo-react-native

### Screenshots and Videos

![Image (1)](https://github.com/user-attachments/assets/b9294099-15f3-4012-a8d8-0f21cde38a39)
![Image](https://github.com/user-attachments/assets/b6ca8821-b995-4692-a65b-6119570f1d07)
Repository: godot
Issue: Physics: collision pass through between `StaticBody3D` w/ `ConcaveCollisionShape3D` and `RigidBody3D` with `ConvexPolygonShape3D`
Labels: bug,topic:physics,topic:3d

### Tested versions

Reproducible in 4.3 and 4.4dev5.

### System information

W11

### Issue description

As per the issue description, a rigid body with two `ConvexCollisionShape3D` registers an initial collision with a static body with a `ConcaveCollisionShape3D` that is actually convex, but then fails to register the second collision when both "legs" are supposed to be on the ground.

https://github.com/user-attachments/assets/599e5e92-ef46-4bfe-bbfb-868f1bf66139

Unfortunately not fixed by #99895.

### Steps to reproduce

Download MRP, make sure to have visible collision shapes, press play and watch the collision fail to happen! Should happen consistently.

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/user-attachments/files/18022818/MRP.zip)
Repository: three.js
Issue: USDZ exporter premultiplies alpha in textures when Texture.premultiplyAlpha == false 
Labels: Addons

### Description

When exporting textures the Canvas 2D API is used to convert Three textures into PNGs. But while input textures usually do not use premultiplied alpha, the [output bitmap](https://html.spec.whatwg.org/multipage/canvas.html#premultiplied-alpha-and-the-2d-rendering-context) of a CanvasRenderingContext2D must always use premultiplied alpha for transparent colors. This implies a lossy conversion step when drawing a non-premultiplied texture to a Canvas 2D rendering context where invisible colors disappear.

I encountered this bug in the USDZ exporter but I suspect that other exporters (like the GLTF exporter) have the same bug.


### Reproduction steps

1. Run the [live example](https://jsfiddle.net/ymtn56hv/)
2. Open the automatically downloaded USDZ in macOS Preview or iOS QuickLook
3. Check for [this defect](https://github.com/KhronosGroup/glTF-Sample-Assets/tree/main/Models/AlphaBlendModeTest#problem-premultiplied-alpha) on the checkmark.

### Code

```js
// code goes here
```


### Live example

https://jsfiddle.net/ymtn56hv/

### Screenshots

<img width="1021" alt="Bildschirmfoto 2024-12-05 um 13 09 33" src="https://github.com/user-attachments/assets/3c01f79e-428c-4ca7-b704-8c2facb3c75c">


### Version

r171

### Device

Desktop

### Browser

Chrome

### OS

MacOS
Repository: vscode
Issue: Git - Improve algorithm for picking the base branch it uses when populating Source Control Graph in Auto mode
Labels: feature-request,git


Type: <b>Feature Request</b>

I contribute to microsoft/vscode through my tracking repo gjsjohnmurray/vscode.
```
> git remote -v
origin  https://github.com/gjsjohnmurray/vscode.git (fetch)
origin  https://github.com/gjsjohnmurray/vscode.git (push)
upstream        https://github.com/microsoft/vscode.git (fetch)
upstream        https://github.com/microsoft/vscode.git (push)
```
When I want to start a branch for a PR here's what I do:

1. On GH update gjsjohnmurray/vscode:main from microsoft/vscode:main
2. Checkout main
3. Pull to update my local
4. Create my new fix-XXX branch in VS Code
5. Make some changes, stage them, commit them and push them to create origin/fix-XXX
6. Make some more changes.

The Auto mode of the Source Control Graph shows me the following 3 branches:
- fix-XXX
- origin/fix-XXX
- origin/main

Instead of origin/main I would like Auto mode to show upstream/main because that's where the commits of merged PRs from other contributers will first show up. They'll only reach my tracking repo (i.e. origin/main) when I get around to repeating step 1 of my original list above.

I propose that the algorithm here should (perhaps optionally) move one step upstream when establishing the `branch.fix-XXX.vscode-merge-base` Git config setting.

VS Code version: Code - Insiders 1.96.0-insider (6567c244f90af8e31d9250e8f9a757b58565649a, 2024-12-05T05:04:06.424Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: flutter
Issue: [pigeon] Implement a useful to-string method for `PigeonError`
Labels: package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

See https://github.com/flutter/flutter/issues/159843 for an example where Swift code logged a `PigeonError` via string interpolation, and it was not useful because it was just the class name. For each output language where we make a custom error object, we should implement whatever that language's version of `toString` is so that log messages will have useful output, as logging errors is a common use case, so we should make it easy.
Repository: pytorch
Issue: Feature Request - Backport torch.special.gammainc for Backward Compatibility
Labels: triaged,module: python frontend

### 🚀 The feature, motivation and pitch

The torch.special.gammainc function, which computes the regularized lower incomplete gamma function, currently lacks backward compatibility support (actually, lack the grad w.r.t. input). This function is essential for various statistical computations, like gamma-related probability calculations.

### Alternatives

It has been implemented by tensorflow.math.igamma. Some related functions can be found in xla and Eigen.

### Additional context


![PixPin_2024-12-05_20-38-23](https://github.com/user-attachments/assets/c20c1881-889a-4d3d-8184-dbf28677d534)



cc @albanD
Repository: vscode
Issue: Update Button missing
Labels: install-update,under-discussion


Type: <b>Bug</b>

check for update button missing from my vs code's help option thus i dont have any method to update my vscode

VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.26100
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 4600H with Radeon Graphics          (12 x 2994)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|7.42GB (1.15GB free)|
|Process Argv|--crash-reporter-id 809bf1f0-42f4-4e6e-94d4-ab4475883412|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (32)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-tailwindcss|bra|0.12.15
es7-react-js-snippets|dsz|4.4.3
bracket-pair-toggler|dzh|0.0.3
prettier-vscode|esb|11.0.0
code-runner|for|0.12.2
solidity|Jua|0.0.179
debugpy|ms-|2024.0.0
python|ms-|2024.2.1
vscode-pylance|ms-|2024.3.2
jupyter|ms-|2023.10.1100000000
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.19
vscode-jupyter-cell-tags|ms-|0.1.8
vscode-jupyter-slideshow|ms-|0.1.5
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
tkinter-snippets|Nik|2.0.2
hardhat-solidity|Nom|0.7.3
material-icon-theme|PKi|5.14.1
LiveServer|rit|5.7.9
tabnine-vscode|Tab|3.199.0
cmake|twx|0.0.17
vscode-lldb|vad|1.11.1
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.3.1
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-pack|vsc|0.29.0
qf|Wsc|6.8.122
JavaScriptSnippets|xab|1.8.0
vscode-react|zha|0.2.2

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

```

</details>

<!-- generated by issue reporter -->
Repository: angular
Issue: Found lots of logical errors in  "Hierarchical injectors" doc
Labels: area: docs

### Which @angular/* package(s) are the source of the bug?

docs

### Is this a regression?

No

### Description

It's so hard to read [this doc](https://angular.dev/guide/di/hierarchical-dependency-injection#example-elementinjector-use-cases), because there are lots of errors (at least, I think they are errors). I can't list all of them, let me for example:
1.
![Image](https://github.com/user-attachments/assets/0e97eb64-8770-4ee3-85b1-b4be981e35ad)
2.
![Image](https://github.com/user-attachments/assets/8a31a092-aca9-4f1c-bc64-029c4d4a22de)




### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_
Repository: realworld
Issue: [Bug]: Documentation: Link to API spec broken
Labels: bug

### Relevant scope

Other: describe below

### Description

1. Open https://realworld-docs.netlify.app/introduction/
2. Click on "API spec"\
    ![image](https://github.com/user-attachments/assets/e0d4d57e-0fe9-4874-bce5-5f759c296226)
3. See 404 (https://realworld-docs.netlify.app/introduction/specs/backend-specs/introduction)

The link should be https://realworld-docs.netlify.app/specifications/backend/introduction/

---

I did not find a `docs` folder here - and the repository https://github.com/gothinkster/realdworld-docs was empty. Therefore, I filed this issue.
Repository: rust
Issue: compiletest: Detect unused auxiliary crates?
Labels: C-enhancement,T-bootstrap,A-compiletest

There are some auxiliary crates that are unused in the `tests` directory. I think it would be nice if compiletest could detect these and complain about them in some way.

This might be difficult due to ignored tests, or tests that are otherwise not run, which don't load enough information to know which auxiliary tests are used.

If it ends up being technically challenging, perhaps someone could just manually go through and clean up the orphans?
I've been intending to do that, but just haven't been able to make the time.

Example: https://github.com/rust-lang/rust/blob/master/tests/ui/auxiliary/default-ty-param-cross-crate-crate.rs
Repository: react
Issue: [Compiler Bug]: Properties added to hook functions are removed
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgDMoA7OXASwhPyjAQGUIBbBXACwpIHMAKASnzAAOjXxxqkADYIAdFIh8A5OwQBPJf1H4AvqNF1GLNpx6zWuAIYATS1fwBefEoDu7OwgBuCGEv0kMbDx8awRCSygpAmIySmp8AFk1AEFMTAEhbVp6JgtTPi0SLJg2WBoAHmsKTwA+AAkEKQV8AHUcKWshQ1yTLm5zNhs7Sx1ygHoq2oBuUT0SEB0gA

### Repro steps

Properties added to hook functions get removed by the Compiler, and trigger the [rule](https://react.dev/reference/rules/react-calls-components-and-hooks#never-pass-around-hooks-as-regular-valueseslint(react-compiler/react-compiler) below:

```
Hooks may not be referenced as normal values, they must be called.
See https://react.dev/reference/rules/react-calls-components-and-hooks#never-pass-around-hooks-as-regular-valueseslint(react-compiler/react-compiler)
```

I understand why this would be triggered for other scenarios where the hooks are referenced as normal values, but is this case really a violation of hook rules in React? It's not listed as a "bad example" in the React docs. If it is, then the compiler and the linter behavior is correct and expected, but can't help but wonder if this is really an issue and not an oversight?

---

For context, I use this pattern in one of my apps that uses TanStack's React Query:

```tsx
import { useQuery } from "@tanstack/react-query"
import { api } from "~/server/api"

export const useGetClient = (id: string) => {
  const query = useQuery({
    queryKey: useGetClient.queryKey(id),
    queryFn: async () => {
      const data = await api.getClient(id)
      return data
    },
  })

  return query
}

useGetClient.queryKey = (id: string) => ["client", id]
```

Attaching the `queryKey` function to the hook like this provides a nice developer experience because we don't need a separate import or a convention-based pattern for figuring out what the query key of a given query is.

We migrated to this pattern away from the pattern we used before where `queryKey` functions were separate objects/functions.

Thanks!


### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

19.0.0-beta-df7b47d-20241124
Repository: angular
Issue: "Input is required but no value is available yet" with toObservable if the content is dynamic
Labels: area: core,area: forms,state: needs more investigation,core: reactivity,cross-cutting: signals

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Just updated to Angular v19 and started to experience an error. Created an example with as minimal code as possible. Unfortunately it doesn't make too much sense without additional context, but it is what it is.

So the setup is the following:
- We have a directive that has a required input (`ModelDirective`)
- We have a component that queries a `ModelDirective` and uses its required input (`FormFieldComponent`)
- We also need to turn that input signal into an rxjs observable (for reasons that is not obvious by the example)

The problem is observed within the `toObservable` but only if the queried directive is created dynamically within a dynamically created component. If you run the example, you can see that the input is actually set properly - if we directly use the computed signal, its value is successfully displayed. However, once we try to read the observable's value, an error is thrown.

If, however, the directive or the owning component is available without any condition, everything works fine (there is a commented line in the example template).

This setup was working fine in Angular v18.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-vjskep?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
ERROR RuntimeError: NG0950: Input is required but no value is available yet.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.0.3
Node: 20.11.1
Package Manager: npm 10.2.4
OS: win32 x64

Angular: 19.0.3
... animations, cli, common, compiler, compiler-cli, core
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1800.3
@angular-devkit/build-angular   19.0.3
@angular-devkit/core            18.0.3
@angular-devkit/schematics      18.2.11
@angular/cdk                    19.0.2
@schematics/angular             18.2.11
ng-packagr                      19.0.1
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.15.0
```

### Anything else?

_No response_
Repository: tensorflow
Issue: [XLA] TF XLA outputs abnormal value when compiling `Embedding`
Labels: stat:awaiting tensorflower,type:bug,comp:xla,TF 2.18

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

nightly

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

For `Embedding` operator, when I set the `input_dim=1` (which means it indexed from 0 to 0), the output always returns **0 without XLA**.

After compilation, the outputs are usually some random tensors.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

tf.random.set_seed(42)
x = tf.constant([1])


# uncompiled model
class Model(tf.keras.Model):

    def __init__(self):
        super(Model, self).__init__()
        self.embedding = tf.keras.layers.Embedding(1, 1)

    def call(self, x):
        output = self.embedding(x)
        return output


m = Model()

output1 = m(x)


# compiled model
class Model(tf.keras.Model):

    def __init__(self):
        super(Model, self).__init__()
        self.embedding = tf.keras.layers.Embedding(1, 1)

    @tf.function(jit_compile=True)
    def call(self, x):
        output = self.embedding(x)
        return output


m = Model()
output2 = m(x)

print(output1)
print(output2)
```


### Relevant log output

```shell
tf.Tensor([[0.]], shape=(1, 1), dtype=float32)
tf.Tensor([[-0.00567592]], shape=(1, 1), dtype=float32)
```
Repository: TypeScript
Issue: "Debug Failure. False expression." when using default export from js file
Labels: Bug

### 🔎 Search Terms

debug failure false expression export default composite allowjs js

### 🕗 Version & Regression Information

- This changed between versions 5.6.2 and 5.7.2

### ⏯ Playground Link

https://stackblitz.com/edit/ts-false-expression-tqxlxy?file=tsconfig.json,package.json

### 💻 Code

```js
// In a JS file
export default console; 
```
The error also seems to happen if you replace `console` with anything from `globalThis` (screen, scroll, fetch, etc.)

TSConfig.json:
```json
    "composite": true,
    "allowJs": true,
```

### 🙁 Actual behavior

Running tsc results in this error:
```
> tsc

Error: Debug Failure. False expression.
    at Object.isUndefinedIdentifierExpression (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:50211:15)
    at typeFromExpression (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:132377:22)
    at serializeTypeOfExpression (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:132107:20)
    at Object.serializeTypeOfDeclaration (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:132131:16)
    at serializeTypeForDeclaration (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:52640:41)
    at serializeMaybeAliasAssignment (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:54015:19)
    at serializeAsAlias (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:53899:13)
    at serializeSymbolWorker (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:53255:11)
    at serializeSymbol (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:53119:11)
    at eval (/home/projects/ts-false-expression-tqxlxy/node_modules/typescript/lib/_tsc.js:53089:11)

Node.js v18.20.3
```

### 🙂 Expected behavior

No Error :-)

### Additional information about the issue

I see this both locally and in stackblitz. I don't know how to reproduce in the playground because it only seems to happen when using a JS file.

This does not cause an error:
```
const thing = console;
export default thing;
```
Repository: rust
Issue: Update tests/ui/codegen/target-cpus.rs after upgrading to LLVM 20
Labels: C-cleanup,A-LLVM,A-testsuite,T-compiler

LLVM 20 is adding a new target CPU for WebAssembly (`lime1`), which changes the output of that test.

https://github.com/rust-lang/rust/pull/133910 temporarily modifies the test to accept the output of both LLVM versions, but that should be reverted after upgrading to LLVM 20.

@rustbot label: +A-llvm