Processed: lowering the severity, package not used to build the affected package

Processing commands for cont...@bugs.debian.org: > severity 994228 important Bug #994228 [gfortran-11] gfortran-11: generates incorrect Iftran compiler Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 994228: https://bugs.

Bug#994292: g++-11: Segfault when defining a module exporting a std::string

Package: g++-11 Version: 11.2.0-4 Severity: normal Dear Maintainer, * What led up to the situation? When defining a simple module in which a std::string is exported the program compiles correctly but segfaults when it's run. When (instead of a std::string) objects like std::vector or std::ifs

[Bug libffi/28036] libffi executable stack (missing .note.GNU-stack on .o files)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28036 --- Comment #10 from Andreas Schwab --- Note that riscv and nios2 are noexec-stack by default, thus do not need a stack note. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug libffi/28036] libffi executable stack (missing .note.GNU-stack on .o files)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28036 --- Comment #9 from Andrew Pinski --- (In reply to Andrew Pinski from comment #8) > These are the ones without the note still: > src/bfin/sysv.S > src/cris/sysv.S > src/m32r/sysv.S > src/metag/sysv.S > src/microblaze/sysv.S > src/nios2/sysv.S > s

[Bug libffi/28036] libffi executable stack (missing .note.GNU-stack on .o files)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28036 --- Comment #8 from Andrew Pinski --- These are the ones without the note still: src/bfin/sysv.S src/cris/sysv.S src/m32r/sysv.S src/metag/sysv.S src/microblaze/sysv.S src/nios2/sysv.S src/or1k/sysv.S src/riscv/sysv.S src/xtensa/sysv.S -- You a