[Bug debug/90109] gstabs flag generates wrong entry for long on x86_64

2019-04-17 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109 --- Comment #5 from Jim Wilson --- Stabs requires that we emit info for all of the base types at the start. But if one of the base types does not exist for a 32-bit K C target, then we are struck, as that can't be described. And if we can't

[Bug debug/90109] gstabs flag generates wrong entry for long on x86_64

2019-04-17 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug debug/90109] gstabs flag generates wrong entry for long on x86_64

2019-04-17 Thread nebiun at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109 --- Comment #3 from nebiun at hotmail dot com --- Sorry, but the bug is not related to the wrong dimension of a type, but to the fact that the bitsize of the same type (K type: long, not long long or double or a user type) is showed as 32 bit as

[Bug debug/90109] gstabs flag generates wrong entry for long on x86_64

2019-04-16 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109 --- Comment #2 from Jim Wilson --- long long and long double did not exist when stabs was invented. Also, 64-bit machines and C++ did not exist at the time. Also, unfortunately, stabs wasn't designed to be extensible. So there is no way to

[Bug debug/90109] gstabs flag generates wrong entry for long on x86_64

2019-04-16 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109 Richard Biener changed: What|Removed |Added CC||wilson at gcc dot gnu.org --- Comment