All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.15.2 build error on AMD64
Date: Sun, 29 Jun 2014 22:05:29 +0100	[thread overview]
Message-ID: <53B07F99.40600@linicks.net> (raw)
In-Reply-To: <20140629194403.GB12943@pd.tnic>

On 29/06/14 20:44, Borislav Petkov wrote:
>> This then is an old(er) version of GCC issue (but I dunno what).
>
> Right, so the error points at
>
> __spin_lock_mb_cache_entry(struct mb_cache_entry *ce)
> {
>   spin_lock(bgl_lock_ptr(mb_cache_bg_lock,			<---
>    (hash_64((unsigned long)ce, __builtin_log2(8)))));
> }
>
> somewhere here and I'd guess that old gcc is issuing some lib function
> which uses SSE. And after we disabled all FPU stuff in the kernel with
> b399fe355b30 ("x86: Disable generation of traditional x87 instructions")
> that would issue such an error.
>
> And I was about to point at that __builtin_log2 thing which looked
> suspicious and found this by chance:
>
> http://lkml.kernel.org/r/1401471304-37479-1-git-send-email-tmac@hp.com
>
> You could test this patch with that old gcc 4.2.x as it looks like a
> good candidate for a fix for your issue.

Thanks Boris, but unfortunately I had to trash GCC 4.2.4 to build the 
new 4.7.4 version - so I can't test the patch :(

At least this issue is now on record so others will not need to go to 
penalties.

Many thanks,

Nick
-- 
"A bug in the code is worth two in the documentation."
FSF Associate Member 5508
http://linicks.net/
http://pi.linicks.net/

  reply	other threads:[~2014-06-29 21:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28  9:52 3.15.2 build error on AMD64 Nick Warne
2014-06-28 10:12 ` Borislav Petkov
2014-06-28 10:26   ` Nick Warne
2014-06-28 10:55     ` Nick Warne
2014-06-28 12:23       ` Borislav Petkov
2014-06-28 13:09         ` Nick Warne
2014-06-29 19:06           ` Nick Warne
2014-06-29 19:44             ` Borislav Petkov
2014-06-29 21:05               ` Nick Warne [this message]
2014-06-29 21:24                 ` Borislav Petkov
2014-06-30 13:26                   ` Borislav Petkov
2014-06-30 18:51                     ` Nick Warne
2014-06-30 19:23                       ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53B07F99.40600@linicks.net \
    --to=nick@linicks.net \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.