All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: libunwind support is broken on MIPS64 n32
Date: Mon, 1 Dec 2014 12:33:42 +0000	[thread overview]
Message-ID: <547C6026.2080501@imgtec.com> (raw)
In-Reply-To: <1417436666-54652-1-git-send-email-Vincent.Riera@imgtec.com>

Also, the former patch was a bit weird. In the commit log you said you
wanted to disable libunwind support for MIPS64, but you only did it for
MIPS64 Little Endian (BR2_mips64el). Why only the little endian variant
and not both big and little endian variants?

Anyway, this is not related to the endianess or the bitness. It's
related to the ABI. In the bug report is explained that it fails only
for the n32 ABI because libunwind assumes a 64bit word size for all
MIPS64 variants, which is wrong. MIPS64 n32 has a 32bit word size. Then,
xorg-server tries to do a conversion of a 64bit variable provided by
libunwind into a (void *), which is 32bit in MIPS64 n32, and it fails
with a message like this one:

backtrace.c:90:20: error: cast to pointer from integer of different size
[-Werror=int-to-pointer-cast]

-- 
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com

  reply	other threads:[~2014-12-01 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 12:24 [Buildroot] [PATCH] xserver_xorg-server: libunwind support is broken on MIPS64 n32 Vicente Olivert Riera
2014-12-01 12:33 ` Vicente Olivert Riera [this message]
2014-12-01 12:38 ` Peter Korsgaard

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=547C6026.2080501@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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.