Target independent tests are always best, but pulling together one that is
specific to a target is usually still good enough. Especially if it's an
x86 target given how often those are tested by the developer community as a
whole.
I think for #1 in your posting, verifying that we issue the proper warning
should be sufficient. Use the dg framework test and this marker:
/* { dg-require-named-sections } */
Thanks! That helps, and I see someone has attached a testcase to the
bugzilla in an attempt to move this forward.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61848#c18
I'll be happy if someone else takes over the bugzilla. I've been on
vacation, and should spend time over the next few weeks on the
binutils 2.25 release rather than trying to push gcc patches.