netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Patrick McHardy <kaber@trash.net>
Cc: bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [Bugme-new] [Bug 18942] New: change to include/linux/netdevice.h prevents compilation for ARM architecture with AEABI enabled
Date: Wed, 22 Sep 2010 02:01:13 -0700	[thread overview]
Message-ID: <20100922020113.b6ff0fd6.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-18942-10286@https.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 22 Sep 2010 08:39:05 GMT bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=18942
> 
>            Summary: change to include/linux/netdevice.h prevents
>                     compilation for ARM architecture with AEABI enabled
>            Product: Platform Specific/Hardware
>            Version: 2.5
>     Kernel Version: 2.6.35.4
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: ARM
>         AssignedTo: linux-arm-kernel@lists.arm.linux.org.uk
>         ReportedBy: ilya@total-knowledge.com
>         Regression: No
> 
> 
> I am trying to compile the latest kernel, and am running into the following
> error:
> In file included from include/linux/icmpv6.h:173,
>                  from include/linux/ipv6.h:220,
>                  from include/net/ipv6.h:16,
>                  from include/linux/sunrpc/clnt.h:25,
>                  from include/linux/nfs_fs.h:48,
>                  from init/do_mounts.c:20:
> include/linux/netdevice.h:1005: error: width of 'reg_state' exceeds its type
> include/linux/netdevice.h:1010: error: width of 'rtnl_link_state' exceeds its
> type
> 
> 
> There was a change not too long ago, which converted reg_state to a bitfield,
> which apparently doesn't work when -mabi=aapcs.
> I tested it with a gcc versions 4.2.0, 4.4.2, and 4.4.4 and it holds true for
> all of them.
> 
> Here is simple test case:
> struct test {
>         enum { NETREG_UNINITIALIZED=0,
>         } reg_state:16;
> };
> 
> int main(int argc, char** argv)
> {
>         struct test tt;
>         tt.reg_state=NETREG_UNINITIALIZED;
>         return 0;
> }
> 
> Compiles without -mabi=aapcs option, fails with.
> 

Bummer.  I guess that this abi requires that enums have `int' width for
some reason?

Does -mabi=aapcs actually get used, officially?  All I can see in
Linus's tree is

z:/usr/src/linux-2.6.36-rc5> grep -r aapcs .
./arch/arm/Makefile:CFLAGS_ABI  :=-mabi=aapcs-linux -mno-thumb-interwork


           reply	other threads:[~2010-09-22  9:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-18942-10286@https.bugzilla.kernel.org/>]

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=20100922020113.b6ff0fd6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kaber@trash.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).