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/15505] ARM glibc missing __aeabi_ctype_table_C and __aeabi_ctype_table_
Date: Fri, 31 May 2013 19:24:00 -0000	[thread overview]
Message-ID: <bug-15505-131-FQnaQxWXOL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15505-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The point of the CLIBABI symbols (such as the ones in this bug report) is 
to support .o files that can be used with more than one C library 
implementation.  The glibc headers can't be used to compile such objects, 
but given objects built with C library headers that support 
_AEABI_PORTABILITY_LEVEL != 0, it should be possible to link those objects 
with glibc and have the code work as expected.

The symbols intended for compiler rather than library portability of .o 
files are generally those defined in RTABI; most of those are in libgcc, 
with only a few such as __aeabi_memcpy* and __aeabi_read_tp being in 
glibc.

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


  parent reply	other threads:[~2013-05-31 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 20:46 [Bug ports/15505] New: " jsm28 at gcc dot gnu.org
2013-05-25 12:57 ` [Bug ports/15505] " bugdal at aerifal dot cx
2013-05-31 19:24 ` joseph at codesourcery dot com [this message]
2013-05-31 19:30 ` bugdal at aerifal dot cx
2013-05-31 19:36 ` joseph at codesourcery dot com
2014-02-08  1:58 ` [Bug libc/15505] [arm] " jsm28 at gcc dot gnu.org
2014-06-13 17:41 ` 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-15505-131-FQnaQxWXOL@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).