public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/15705] MicroBlaze mmap64 incorrect page shift
Date: Wed, 05 Feb 2014 23:16:00 -0000	[thread overview]
Message-ID: <bug-15705-131-QzENHHMzoO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15705-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15705

--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
It looks like the kernel changed the ABI incompatibly in 3.13.  That means 
a more complicated fix is needed, meaning that if an __ASSUME_* macro is 
defined (which would be for --enable-kernel=3.13.0 or later) then you can 
just use the generic mmap64.c, but otherwise working reliably means a 
runtime check on GLRO(dl_osversion) >= 0x030d00 to determine the ABI in 
use (cf. the ARM runtime check for an incompatible change in signal frame 
unwinding).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-02-05 23:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 20:22 [Bug ports/15705] New: " jsm28 at gcc dot gnu.org
2014-02-05  7:41 ` [Bug ports/15705] " cvs-commit at gcc dot gnu.org
2014-02-05  7:52 ` david.holsgrove at xilinx dot com
2014-02-05 11:23 ` cvs-commit at gcc dot gnu.org
2014-02-05 22:53 ` bugdal at aerifal dot cx
2014-02-05 23:16 ` joseph at codesourcery dot com [this message]
2014-02-05 23:29 ` david.holsgrove at xilinx dot com
2014-02-05 23:34 ` bugdal at aerifal dot cx
2014-02-05 23:45 ` joseph at codesourcery dot com
2014-02-05 23:49 ` david.holsgrove at xilinx dot com
2014-02-06  1:23 ` cvs-commit at gcc dot gnu.org
2014-02-17 18:17 ` [Bug libc/15705] [microblaze] " jsm28 at gcc dot gnu.org
2014-06-13  9:47 ` fweimer at redhat dot com

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=bug-15705-131-QzENHHMzoO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).