On 11/13/20 7:57 AM, Austin Morton wrote: > On the contrary, as a user of GCC I would much prefer a consistent > behavior for #pragma region based purely on GCC version.
You can get consistent behavior with a command line argument and it's much more useful over time as the world changes. > > IE, so you can tell people: > "just update to GCC X.Y and those warnings will go away" > rather than: > "update to GCC X.Y and pass some new flags - but make sure > not to pass them to old GCC versions, since that will generate > a new warning" I'm aware of those benefits. But I would still claim that embedding knowledge of other toolchain's pragmas into GCC itself is just plain wrong from a design standpoint. A flag to allow specifying pragmas to ignore would be much more useful and gets you the same level of consistency with a much higher degree of control and future proofing. Being able to specify them in a file would be even better (IMHO) I'm not going to ACK this patch. However, I won't object if someone else wants to ACK it. Jeff
