[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #11 from Uroš Bizjak --- (In reply to Andy Lutomirski from comment #9) > I'm a bit late to the party, but this patch seems dubious to me. > __get_cpuid_max() fails to distinguish between CPUs that have max level 0 > (although I

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #10 from Christos Zoulas --- On Jun 27, 4:26pm, gcc-bugzi...@gcc.gnu.org ("luto at kernel dot org") wrote: -- Subject: [Bug target/68491] libgcc calls __get_cpuid with 0 level breaks o | I'm a bit late to the party, but this patch

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 Andy Lutomirski changed: What|Removed |Added CC||luto at kernel dot org --- Comment #9

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 Uroš Bizjak changed: What|Removed |Added CC||tedheadster at gmail dot com --- Comment

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 Uroš Bizjak changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #6 from uros at gcc dot gnu.org --- Author: uros Date: Wed May 3 20:00:50 2017 New Revision: 247566 URL: https://gcc.gnu.org/viewcvs?rev=247566=gcc=rev Log: Backport from mainline 2017-05-01 Uros Bizjak

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #5 from uros at gcc dot gnu.org --- Author: uros Date: Wed May 3 18:19:28 2017 New Revision: 247561 URL: https://gcc.gnu.org/viewcvs?rev=247561=gcc=rev Log: Backport from mainline 2017-05-01 Uros Bizjak

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #4 from uros at gcc dot gnu.org --- Author: uros Date: Tue May 2 20:36:26 2017 New Revision: 247523 URL: https://gcc.gnu.org/viewcvs?rev=247523=gcc=rev Log: Backport from mainline 2017-05-01 Uros Bizjak

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 Uroš Bizjak changed: What|Removed |Added Target|i?86-*-*|x86 Status|UNCONFIRMED

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Mon May 1 15:38:14 2017 New Revision: 247439 URL: https://gcc.gnu.org/viewcvs?rev=247439=gcc=rev Log: PR target/68491 * config/i386/cpuid.h (__get_cpuid): Always

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #2 from Christos Zoulas --- Created attachment 41284 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41284=edit Amended cpuid patch. Here's an amended patch against the trunk. Also sent mail to gcc-patches@

[Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 --- Comment #1 from Andrew Pinski --- Patches should goto gcc-patches@ and should be based off the trunk of GCC.