All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arvind Sankar <nivedita@alum.mit.edu>
To: Arvind Sankar <nivedita@alum.mit.edu>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Tom Anderson" <thomasanderson@google.com>,
	"Hans Verkuil" <hansverk@cisco.com>,
	"Manasi Navare" <manasi.d.navare@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Error building v5.5-git on PowerPC32 - bisected to commit 7befe621ff81
Date: Thu, 6 Feb 2020 18:33:26 -0500	[thread overview]
Message-ID: <20200206233325.GA3036478@rani.riverdale.lan> (raw)
In-Reply-To: <20200206231211.GA2976063@rani.riverdale.lan>

On Thu, Feb 06, 2020 at 06:12:13PM -0500, Arvind Sankar wrote:
> On Thu, Feb 06, 2020 at 04:46:52PM -0600, Larry Finger wrote:
> > When building post V5.5 on my PowerBook G4 Aluminum, the build failed with the 
> > following error:
> 
> It's not that the attributes are wrong. The problem is that BUILD_BUG_ON
> requires a compile-time evaluatable condition. gcc-4.6 is apparently not
> good enough at optimizing to reduce that expression to a constant,
> though it was able to do it with the array accesses.

Should have noted, it fails on x86 too with gcc-4.6.4, not specific to PPC.

  reply	other threads:[~2020-02-06 23:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 22:46 Error building v5.5-git on PowerPC32 - bisected to commit 7befe621ff81 Larry Finger
2020-02-06 23:12 ` Arvind Sankar
2020-02-06 23:33   ` Arvind Sankar [this message]
2020-02-07  0:29     ` Larry Finger
2020-02-07  4:18       ` Arvind Sankar
2020-02-07 13:12 ` Ville Syrjälä
2020-02-07 16:22   ` Larry Finger

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=20200206233325.GA3036478@rani.riverdale.lan \
    --to=nivedita@alum.mit.edu \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hansverk@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manasi.d.navare@intel.com \
    --cc=thomasanderson@google.com \
    --cc=ville.syrjala@linux.intel.com \
    /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.