Subject : New x86 warning
Submitter : Jeff Garzik <firstname.lastname@example.org>
Date : 2009-04-22 6:46
References : http://marc.info/?l=linux-kernel&m=124038280020950&w=4
Handled-By : Andi Kleen <email@example.com>
Patch : http://patchwork.kernel.org/patch/19330/
Patch : http://patchwork.kernel.org/patch/19406/
Notify-Also : Ingo Molnar <firstname.lastname@example.org>
This entry is being used for tracking a regression from 2.6.29. Please don't
close it until the problem is fixed in the mainline.
On Sunday 26 April 2009, Ingo Molnar wrote:
> * Rafael J. Wysocki <email@example.com> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > The following bug entry is on the current list of known regressions
> > from 2.6.29. Please verify if it still should be listed and let me know
> > (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13185
> > Subject : New x86 warning
> > Submitter : Jeff Garzik <firstname.lastname@example.org>
> > Date : 2009-04-22 6:46 (4 days old)
> > References : http://marc.info/?l=linux-kernel&m=124038280020950&w=4
> I saw this warning with certain GCC versions for several kernel
> cycles, so it's not any recent change that triggers this and it is
> not a regression.
> GCC is simply wrong here - i have posted a workaround for that but
> it is too ugly to be merged upstream.
> > Handled-By : Andi Kleen <email@example.com>
> > Patch : http://patchwork.kernel.org/patch/19330/
> > http://patchwork.kernel.org/patch/19406/
> This patch regresses on older GCC versions and doesnt really address
> the GCC false positive warning either, it just removes the inline
> function that triggers the warning.