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 |
|---|---|---|
| Question | File an issue about unexplained behavior | [QUESTION] |
If you have a question, please check the following first:
- Check if your question has already been answered in the FAQ section.
- Make sure you've read the documentation. Your issue may be addressed there.
- If those resources didn't help and you only have a short question (not a bug report), consider asking in the Gitter chat room
- Search the issue tracker, including the closed issues, to see if your question has already been asked/answered. +1 or comment if it has been asked but has no answer.
- If you have a more complex question which is not answered in the previous items (or not suitable for chat), please fill in the details below.
- Include a self-contained and minimal piece of code that illustrates your question. If that's not possible, try to make the description as clear as possible.
After reading, remove this checklist.