Status Update
No update yet.
Comments
ze...@google.com
i donnot understand why is the data the same?
ms...@gmail.com
ap...@google.com
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
ze...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
ze...@google.com
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。
as for Android build,all versions have it.
I dont reprodouce this issue.
what may be the cause of this issue?please
ms...@gmail.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ms...@gmail.com
Thanks for reporting this issue.
COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.
Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.
sg...@google.com
We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.
ap...@google.com
ap...@google.com
Branch: main
commit 24659d5eae579cd1db20ffe88f6a634a333e9bfe
Author: Christoffer Adamsen <christofferqa@google.com>
Date: Wed Jan 03 16:11:05 2024
Reland "Disable redundant load elimination in debug mode"
Bug:
Bug:
Change-Id: I1c4fba711609183130735f8b93d0dbe627dec1c1
M src/main/java/com/android/tools/r8/ir/conversion/passes/CodeRewriterPassCollection.java
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
M src/test/java/com/android/tools/r8/regress/b316744331/Regress316744331Test.java
ap...@google.com
Branch: main
commit c0b9ea0f3b9dd56f6e301b96d48eb1c583497f24
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Mon Jan 08 10:44:08 2024
Update 911-get-stack-trace after disabling field load elimination
D8 8.4.5-dev disables redundant field load elimination in debug mode.
Bug: 316744331
Change-Id: Iee10c8656266b41ef108d5da1c1716ac27ea8ef9
Test: existing
M test/911-get-stack-trace/expected-stdout.txt
ap...@google.com
Branch: 8.0
commit 44de2d3b1a19951abccf33e2412d625b11ca437e
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 09:54:22 2024
Version 8.0.75
Bug:
Change-Id: I7347b09a29ba027dabcb999348422802935d24c7
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.0
commit ab8f6074de78773d0a2796a95ee3285cc6598bcf
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 09:49:33 2024
Reland "Disable redundant load elimination in debug mode"
Notice: this cherry pick is written manually as this branch is from
before the introduction of code rewriter passes.
Bug:
Bug:
Change-Id: I1c4fba711609183130735f8b93d0dbe627dec1c1
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
ap...@google.com
Branch: 8.3
commit a7a3e45076d5fa6124376bd48022d4064b148df9
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 14:14:44 2024
Version 8.3.30
Bug:
Change-Id: I7edbb53ca57833a476577c26e766ca7aae001f86
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.3
commit bf16876c41ebee42408696d4be2fb6434f3cf341
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 14:13:53 2024
Reland "Disable redundant load elimination in debug mode"
Notice: this cherry pick is written manually as this branch is from
before the introduction of code rewriter passes.
Bug:
Bug:
Change-Id: I1c4fba711609183130735f8b93d0dbe627dec1c1
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
ap...@google.com
Branch: 8.2
commit fe9c21581262cb92258d217c1c4f52a652e64d4d
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 13:48:00 2024
Reland "Disable redundant load elimination in debug mode"
Notice: this cherry pick is written manually as this branch is from
before the introduction of code rewriter passes.
Bug:
Bug:
Change-Id: I1c4fba711609183130735f8b93d0dbe627dec1c1
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
ap...@google.com
Branch: 8.2
commit fd4b26bdc8af1f07472da2af2114e027e53a0efc
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 13:50:35 2024
Version 8.2.46
Bug:
Change-Id: I880c56fd07902c4697105778150be4cc16cd27a6
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.1
commit 59a7c1ac06e0fed85dd2f4f2a710f11fe433640b
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 12:13:37 2024
Reland "Disable redundant load elimination in debug mode"
Notice: this cherry pick is written manually as this branch is from
before the introduction of code rewriter passes.
Bug:
Bug:
Change-Id: I1c4fba711609183130735f8b93d0dbe627dec1c1
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
ap...@google.com
Branch: 8.1
commit 916a6d04b1c84a95bca923f2ea273fd7d52532fa
Author: Ian Zerny <zerny@google.com>
Date: Tue Jan 09 12:14:41 2024
Version 8.1.78
Bug:
Change-Id: I00bd2fac3a2548883838209d239b7fd200a54da0
M src/main/java/com/android/tools/r8/Version.java
ze...@google.com
A fix has been pushed to 8.0, 8.1, 8.2 and 8.3 branches for R8.
To use one of the fixed versions without AGP updates amend your settings.gradle or settings.gradle.kts file with:
pluginManagement {
buildscript {
repositories {
mavenCentral()
maven {
url = uri("https://storage.googleapis.com/r8-releases/raw")
}
}
dependencies {
classpath("com.android.tools:r8:8.2.46") // <-- Use version matching your AGP here
}
}
}
Since AGP 8, the R8 versions follow those of AGP, so if using AGP 8.2 use the latest version on the R8 8.2 branch (for this
ms...@gmail.com
Thank you for fixing this issue!
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Hedgehog | 2023.1.1 Patch 2
- Android Gradle Plugin 8.2.2
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
so...@google.com
Comment added by automation: A postmortem has been automatically requested for this issue. Please author a postmortem on IRM. See go/android-postmortem-guidance for more context and details, including how to handle the case when this issue does not need a postmortem. If you have any questions not answered by go/android-postmortem-guidance, please email android-hygiene-tpm@, instead of reassigning the fixed bug. Thank you.
an...@google.com
The fixes for this issue are now also available in:
- Android Studio Iguana | 2023.2.1 RC 1
- Android Gradle Plugin 8.3.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
I work on the WALA static analysis framework (https://github.com/wala/WALA ), and we use D8 to test WALA's Dalvik frontend. I've been trying to update to the latest D8 version and I ran into an issue with unexpected dead code elimination. Consider the following (weird) Java code from JLex:
With the old D8 version we were using (2.2.42), the
System.out.printlncalls would be present in the Dalvik bytecode output of D8, even though they are clearly dead code. But with verson 8.2.39, these calls are eliminated. I wouldn't expect D8 alone to be doing this optimization. Here is how we run D8 on a jar:Is the new output expected? I.e., is this level of dead code elimination now "baked in" to D8? Thanks!