[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 --- Comment #7 from Eric Gallager --- Making some more progress on this: https://github.com/gcc-mirror/gcc/compare/master...cooljeanius:gcc:me/PR102665 Some notes: - There are a lot of these; I'm not quite sure how many to include in a single patch, or where I should stop... - I'm currently testing platform based on target, but I'm not quite sure if that's correct? Are these target flags or host flags? - All I've done so far has been to test to make sure that the flags are properly rejected on platforms where they're unsupported; I'd appreciate it if people could help with testing that they're still accepted on platforms where they're supposed to be accepted, though...
[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 --- Comment #6 from Eric Gallager --- WIP: I stubbed in a start on this in my autotools-tinkering branch a bit: https://github.com/gcc-mirror/gcc/commit/c2caa289485edb40eddcd240a7fc655cfd7c38ba (it's got some unrelated parts in it that I'll need to strip out again when cherry-picking it over to my branch for this PR, though...)
[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 --- Comment #5 from Iain Sandoe --- (In reply to Eric Gallager from comment #4) > Hm, looking in gcc/configure.ac (where these are defined), it looks like > there's a bunch of other flags that this bug could apply to, too... Note that I would try to clarify: It is my understanding that the purpose of configure is to isolate the end user from having to know about all the nasty little nooks and crannies of their target. As such it is not a "maintainer preference" to avoid end user having to manipulate many such options but, rather, that if we reach that situation, then the configure script is not doing its job and needs work. As far as I understand things the right behaviour of configure is to choose a correct default value for each option based on the target. The way that the options work it is usually possible to ignore one for a specific target if it does not apply at all. Therefore: 1. making sure defaults are correct is valuable 2. perhaps just ignoring ELF-specific options (for Darwin)is useful (you could, even diagnose that the option has been ignored if the user attempts to set it). 3. As you have noted, there are quite likely more options that could/should/maybe already are ignored for Darwin.
[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 --- Comment #4 from Eric Gallager --- Hm, looking in gcc/configure.ac (where these are defined), it looks like there's a bunch of other flags that this bug could apply to, too...
[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 Eric Gallager changed: What|Removed |Added Last reconfirmed||2022-05-24 Assignee|unassigned at gcc dot gnu.org |egallager at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Eric Gallager --- Mine.
[Bug bootstrap/102665] ELF-specific configure flags should be rejected on non-ELF platforms
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102665 Eric Gallager changed: What|Removed |Added CC||iains at gcc dot gnu.org --- Comment #2 from Eric Gallager --- (this is something discussion with Iain Sandoe prompted me to file, btw, so I'm cc-ing him on this)
