https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80092
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Thomas Schwinge from comment #2) > (In reply to Tom de Vries from comment #0) > > But it's better to introduce effective-target keywords for those features, > > and mark the tests as such. That will reduce the noise rate because of > > unsupported features being used or not due to code generation changes. > > But that will be a rather huge effort to do -- and to keep up to date. Is > that really worth it? The initial amount of tests to process will be large. That would be a huge effort to do, if it would be done manually. However, I would write a script parsing gcc.log or similar to generate those changes. Keeping things up-to-date once there's a script will require little effort, I suppose.
