From: Mark Mitchell <mark@codesourcery.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Thomas Schwinge <thomas@schwinge.name>,
gcc-patches <gcc-patches@gcc.gnu.org>,
thomas@codesourcery.com
Subject: Re: [PATCH] glibc / uclibc / bionic switch vs. non-Linux, GNU-based systems
Date: Mon, 20 Dec 2010 21:06:00 -0000 [thread overview]
Message-ID: <4D0F9F64.3060708@codesourcery.com> (raw)
In-Reply-To: <7ED1339C-9492-45AD-BF72-DE2A6E25139A@codesourcery.com>
On 12/20/2010 6:39 AM, Maxim Kuvyrkov wrote:
>> This alternative patch limits use of linux.opt to those targets
>> for which it is relevant - that is, *-*-linux* (systems using the
>> Linux kernel and an MMU-based ABI), as those are the systems for
>> which alternative libcs may be available withing a single compiler
>> configuration.
>
> The patch looks OK to me, thanks for cleaning this up! Any global
> maintainer wishes to bless it?
Looks good to me.
> Even though it may be debatable that MMU-less systems may benefit
> from multiple C libraries supported within a single compiler
> configuration, it's very clear that definitions of such C libraries
> and corresponding -m<library> options should be located outside of
> linux.opt.
And, I think it's clear that MMU-less systems do benefit from this kind
of functionality in general, though perhaps from different libraries.
Various RTOSes ship with various C libraries, and it's entirely
reasonable that a *-elf configuration have support for multiple run-time
libraries as well.
Thank you,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
prev parent reply other threads:[~2010-12-20 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 15:54 Thomas Schwinge
2010-12-08 16:45 ` Joseph S. Myers
2010-12-08 16:58 ` Thomas Schwinge
2010-12-08 17:28 ` Joseph S. Myers
2010-12-10 12:34 ` Thomas Schwinge
2010-12-14 18:09 ` Ping " Joseph S. Myers
2010-12-20 14:46 ` Ping^2 " Joseph S. Myers
2010-12-20 17:04 ` Maxim Kuvyrkov
2010-12-20 21:06 ` Mark Mitchell [this message]
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=4D0F9F64.3060708@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=maxim@codesourcery.com \
--cc=thomas@codesourcery.com \
--cc=thomas@schwinge.name \
/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).