We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
gcc's STL implementation suffers the same problem, see issue for details. I'm wondering if abseil team plans to resolve it.
This is the link to reproduce STL's issue, replacing with the abseil implementation could reproduce as well.
20230802.1
[~/ray] (master) ubuntu@hjiang-devbox-pg$ uname -a Linux hjiang-devbox-pg 5.15.0-1056-aws #61~20.04.1-Ubuntu SMP Wed Mar 13 17:40:41 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux (myenv) [~/ray] (master) ubuntu@hjiang-devbox-pg$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
[~/ray] (master) ubuntu@hjiang-devbox-pg$ g++ --version g++ (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0 Copyright (C) 2019 Free Software Foundation, Inc.
[~/ray] (master) ubuntu@hjiang-devbox-pg$ bazel --version bazel 6.5.0
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the issue
gcc's STL implementation suffers the same problem, see issue for details.
I'm wondering if abseil team plans to resolve it.
Steps to reproduce the problem
This is the link to reproduce STL's issue, replacing with the abseil implementation could reproduce as well.
What version of Abseil are you using?
20230802.1
What operating system and version are you using?
What compiler and version are you using?
What build system are you using?
Additional context
No response
The text was updated successfully, but these errors were encountered: