------- Comment #6 from fxcoudert at gcc dot gnu dot org 2008-01-19 17:25
-------
(In reply to comment #5)
> I do not have a strong feeling about it, and I would accept it if you
> propose to close this issue.
[...]
> A "-ffake-lack-of-integer-kind-1 option" would have made it easier to
> resolve clashes in interfaces and similar issues.
Yes, I do understand that it would be useful to you. The problem is: there are
so many other similar options that could be useful, once in a lifetime, to
someone, how do we choose which we implement? I suspect your problem is not
very common (lack of kind=1), and that's not worth the cost: at some point, NEC
might add kind=1, and our option becomes useless. Or, on some other platform,
it might be another kind missing, or maybe the kind numbers are just different
even though all integer types are really available, etc.
I'm closing this PR as WONTFIX, as I think others would probably have the same
opinion than mine, but please really feel free to bring the issue to the list
if you think otherwise: we can always reopen the PR.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34804
