../../src/assembly/InflationModel.hpp: Dans l'instanciation de « struct pii::InflationModelBase<pii::NullGraphObserver> » : ../../src/assembly/InflationModel.hpp:152:9: requis depuis ici ../../src/assembly/InflationModel.hpp:120:11: erreur interne du compilateur: Erreur de segmentation 120 | using TreeComposition = ModuleGraphComposition<ObservedModuleGraphPlugin, BlockBase>; | ^~~~~~~~~~~~~~~ Veuillez soumettre un rapport d’anomalies complet, avec la sortie du préprocesseur. Voir <http://bugzilla.redhat.com/bugzilla> pour les instructions. La source convertie par le préprocesseur a été stockée dans le fichier /tmp/ccVh3qLU.out, veuillez l'attacher à votre rapport d'anomalie. Reproducible: Always Steps to Reproduce: The code is proprietary and cannot be submitted for bug reproducability. A minimal working example is not possible (short of substantial funding for the effort). Actual Results: GCC encounters a segmentation fault and fails to compile. Expected Results: It worked on the latest GCC distributed with Fedora 37 (I have no idea what version that was). Preprocessor file attached, as requested in the GCC error message.
Created attachment 1983226 [details] Preprocessor output, as requested by the GCC error message.
Created attachment 1983227 [details] Another instance of preprocessor output, for a different build target.
Created attachment 1983426 [details] Preprocessor output for the same project encountering the same crash on version 13.0.1
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.