| Summary: | sys-devel/gcc - libgcc calls __get_cpuid with 0 level breaks on early 486 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | tedheadster |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491 | ||
| Whiteboard: | masked in 17.0 profiles | ||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 638030 | ||
| Bug Blocks: | |||
|
Description
tedheadster
2017-08-10 19:34:29 UTC
I am rather doubtful that anyone would be running Gentoo on a i486 these days, so this hardly seems worth a backport. I am running on an i486 for regression testing. Testing on old hardware has turned up some bugs that were worth fixing (see "nohz problem with idle time on old hardware" on linux kernel mailing list for an example). While not particularly interesting, the upstream gcc team thought it was worth fixing and backporting. GCC 6.4.0 already has the fix. I would guess a 7.2.0 release is due soon. 5.5.0 is probably farther off, if it even happens. (In reply to Mike Gilbert from comment #3) > GCC 6.4.0 already has the fix. I would guess a 7.2.0 release is due soon. > 5.5.0 is probably farther off, if it even happens. 6.4 and 7.2 are in Gentoo, and 6.4.0 will get stabilized soon. 6.4.0 is stable everywhere. |