This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/19214] Family and model identification for AMD CPU's are incorrect.
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 02 Jun 2016 21:51:48 +0000
- Subject: [Bug libc/19214] Family and model identification for AMD CPU's are incorrect.
- Auto-submitted: auto-generated
- References: <bug-19214-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19214
--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Thu, 2 Jun 2016, amit.pawar at amd dot com wrote:
> Status|RESOLVED |REOPENED
> Resolution|FIXED |---
>
> --- Comment #10 from Amit Pawar <amit.pawar at amd dot com> ---
> After the git commit "f4b6d20366aac66070f1cf50552cf2951991a1e5" FMA4 detection
> fails on AMD CPU's.
That's not a proper reason to reopen a bug.
Has *the original problem reported in the present bug* been fixed? If so,
this bug should remain closed, and a new bug should be opened for the
issue introduced by the fix.
If the original problem was never fixed at all, and the original problem
was thus in fact present in the 2.23 release, then reopening is correct,
but not sufficient; in that case, the entry for that bug in NEWS listing
it as fixed in 2.23 would need removing, and the milestone would need to
be reset.
(If a problem was fixed, then the fix reverted, reopening is correct if
the fix never went into a release - but after a release, it's best to open
a new bug to avoid confusing state about when a bug was fixed.)
--
You are receiving this mail because:
You are on the CC list for the bug.