public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org
Subject: [PATCH 0/3] v2: Experimental patches and musl-libc
Date: Sun, 27 Jul 2014 01:05:00 -0000	[thread overview]
Message-ID: <1406423095-18198-1-git-send-email-bryanhundven@gmail.com> (raw)

This patch series is based on a patch by Timo TerÃs:
    http://patchwork.ozlabs.org/patch/257187/

I ran into a brick wall trying to do this the first time here:
    https://sourceware.org/ml/crossgcc/2014-07/msg00017.html

and this is my attempt to make things more manageable and explicit that these patches are experimental and not supported by crosstool-ng.

As with the previous patch set, this is [RFC].

I have one more patch to send that is more RFC then this set that allows specific patch tuning, but in the meantime this patch set works.

Also, to note my previous patch set:
Currently a minimal armel- is the only target tested. Please let me know your experiences, comments, feedback, and/or suggestions.


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2014-07-27  1:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27  1:05 Bryan Hundven [this message]
2014-07-27  1:05 ` [PATCH 2/3] Add support for musl-libc Bryan Hundven
2014-07-27 23:15   ` Yann E. MORIN
2014-07-27 23:50     ` Bryan Hundven
2014-07-27  1:05 ` [PATCH 3/3] Add musl patches for gcc Bryan Hundven
2014-07-27  1:05 ` [PATCH 1/3] Add main EXPERIMENTAL_PATCHES setting Bryan Hundven
2014-07-27 23:23   ` Yann E. MORIN

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=1406423095-18198-1-git-send-email-bryanhundven@gmail.com \
    --to=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@free.fr \
    /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).