mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com, lowrisc-dev@lists.lowrisc.org
Subject: Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
Date: Sun, 26 Jun 2016 20:57:51 -0400	[thread overview]
Message-ID: <20160627005750.GG10893@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMKF1sq9-Awg+XBn8HY2fuBSzs=e_RxR+fjgRBiHv4kMPzYmfA@mail.gmail.com>

On Sun, Jun 26, 2016 at 03:51:50PM -0700, Khem Raj wrote:
> On Jun 26, 2016 9:12 AM, "Rich Felker" <dalias@libc.org> wrote:
> >
> > On Sat, Jun 18, 2016 at 06:30:17PM +0200, Szabolcs Nagy wrote:
> > > * Masanori Ogino <masanori.ogino@gmail.com> [2016-06-18 22:21:58 +0900]:
> > > > This week, I have tried to run libc-test [1] on Spike with the
> > > > musl-based toolchain, but not succeeded. I found a minor problem with
> > > > recent cpp (I will report it to the maintainer of libc-test later) but
> > >
> > > you have to s/-E/-E -P/ in the makefile
> > >
> > > i was reluctant to do this upstream as it is a non-standard flag.
> 
> Just pin minimum gcc version to 5

libc-test does not depend on gcc much less a particular gcc version.
Ability to apply tests with different compilers is fairly important
since, for some interfaces, a buggy compiler might transform how
they're invoked in invalid ways that result in breakage, and these
sorts of bugs are useful to be able to track down.

Rich


      reply	other threads:[~2016-06-27  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 13:21 Masanori Ogino
2016-06-18 16:30 ` Szabolcs Nagy
2016-06-19 14:52   ` Masanori Ogino
2016-06-26 16:12   ` Rich Felker
2016-06-26 22:51     ` Khem Raj
2016-06-27  0:57       ` Rich Felker [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=20160627005750.GG10893@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=lowrisc-dev@lists.lowrisc.org \
    --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).