c4aaf373aa
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>
22 lines
1.2 KiB
Markdown
22 lines
1.2 KiB
Markdown
---
|
|
name: Question
|
|
about: File an issue about unexplained behavior
|
|
title: "[QUESTION] "
|
|
---
|
|
|
|
If you have a question, please check the following first:
|
|
|
|
1. Check if your question has already been answered in the [FAQ][] section.
|
|
2. Make sure you've read the [documentation][]. Your issue may be addressed there.
|
|
3. If those resources didn't help and you only have a short question (not a bug report), consider asking in the [Gitter chat room][]
|
|
4. 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.
|
|
5. 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.
|
|
6. 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.
|
|
|
|
[FAQ]: http://pybind11.readthedocs.io/en/latest/faq.html
|
|
[documentation]: https://pybind11.readthedocs.io
|
|
[issue tracker]: https://github.com/pybind/pybind11/issues
|
|
[Gitter chat room]: https://gitter.im/pybind/Lobby
|
|
|
|
*After reading, remove this checklist.*
|