mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Po-yi Wang <player@vcn.bc.ca>
To: musl@lists.openwall.com
Subject: Re: will this idea work?
Date: Thu, 25 Jan 2018 12:09:27 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1801251159010.6883@vcn.bc.ca> (raw)
In-Reply-To: <20180125112249.GE4418@port70.net>



On Thu, 25 Jan 2018, Szabolcs Nagy wrote:

> * Po-yi Wang <player@vcn.bc.ca> [2018-01-24 21:16:15 -0800]:
>> the current version of musl (1.1.18), will no longer work with older
>> binutils and gcc, specifically, the arm target. both i486 and ppc seem ok.
>> i have checked older versions of musl, i guess some of them must have worked
>> with gcc-3 binutils-1.15 before. suppose i try to port musl to work with
  (binutils-2.15)(typo)
>> older tools, specially gcc-3.4.5 and binutils-1.15. also assuming, only need
  (binutils-2.15)(typo) 
>> to support older cpu and nothing new. i am guessing porting all the assembly
>> files (*.s) would be sufficient?
>
> yes, porting the asm works, but note that the old
> vfp intrinsics that work in binutils don't work in
> llvm (complain to llvm folks) so it's not possible
> to write asm such that every tool is happy, you
> will need to do some ifdef clang hackery and i'm
> not sure if the '.object_arch' directive works with
> that old binutils.
>
i scanned through the musl mailing list archive, it seemed that
  the minimum supported binutils version has been discussed before, 
around October 15, 2015. what is the current recommended gcc+binutils
version that can support 486,armv5,ppc750?


  reply	other threads:[~2018-01-25 20:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  5:16 Po-yi Wang
2018-01-25 11:22 ` Szabolcs Nagy
2018-01-25 20:09   ` Po-yi Wang [this message]
2018-01-25 20:30     ` Rich Felker
2018-01-25 21:31       ` Po-yi Wang
2018-01-26  2:07         ` Rich Felker
2018-01-26  6:03           ` Po-yi Wang
2018-01-27 22:22           ` A. Wilcox

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=Pine.LNX.4.64.1801251159010.6883@vcn.bc.ca \
    --to=player@vcn.bc.ca \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).