This should help reduce warning spew when building with newer compilers. The pybind11::module type has been renamed pybind11::module_ to avoid conflicts with c++20 modules, according to the pybind11 changelog, so this CL also updates gem5 source to use the new type. There is supposedly an alias pybind11::module which is for compatibility, but we still get linker errors without changing to pybind11::module_. Change-Id: I0acb36215b33e3a713866baec43f5af630c356ee Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/40255 Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu> Reviewed-by: Bobby R. Bruce <bbruce@ucdavis.edu> Tested-by: kokoro <noreply+kokoro@google.com>
1.2 KiB
1.2 KiB
name, about, title
| name | about | title |
|---|---|---|
| Bug Report | File an issue about a bug | [BUG] |
Make sure you've completed the following steps before submitting your issue -- thank you!
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room.
- Include a self-contained and minimal piece of code that reproduces the problem. If that's not possible, try to make the description as clear as possible. a. If possible, make a PR with a new, failing test to give us a starting point to work on!
After reading, remove this checklist and the template text in parentheses below.
Issue description
(Provide a short description, state the expected behavior and what actually happens.)
Reproducible example code
(The code should be minimal, have no external dependencies, isolate the function(s) that cause breakage. Submit matched and complete C++ and Python snippets that can be easily compiled and run to diagnose the issue.)