* [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
@ 2016-06-18 13:21 Masanori Ogino
2016-06-18 16:30 ` Szabolcs Nagy
0 siblings, 1 reply; 6+ messages in thread
From: Masanori Ogino @ 2016-06-18 13:21 UTC (permalink / raw)
To: lowrisc-dev; +Cc: musl
Hello all,
This is the fourth issue of weekly report on porting musl to RISC-V
GSoC project.
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
it is not the main issue preventing the test. I will continue
debugging this weekend.
There is no significant progress on the project this week. I will try
to contact other developers more and more to gain speed.
Have a nice weekend!
[1]: http://nsz.repo.hu/git/?p=libc-test
--
Masanori Ogino
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
2016-06-18 13:21 [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4 Masanori Ogino
@ 2016-06-18 16:30 ` Szabolcs Nagy
2016-06-19 14:52 ` Masanori Ogino
2016-06-26 16:12 ` Rich Felker
0 siblings, 2 replies; 6+ messages in thread
From: Szabolcs Nagy @ 2016-06-18 16:30 UTC (permalink / raw)
To: musl; +Cc: lowrisc-dev
* 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
2016-06-18 16:30 ` Szabolcs Nagy
@ 2016-06-19 14:52 ` Masanori Ogino
2016-06-26 16:12 ` Rich Felker
1 sibling, 0 replies; 6+ messages in thread
From: Masanori Ogino @ 2016-06-19 14:52 UTC (permalink / raw)
To: musl, lowrisc-dev
2016-06-19 1:30 GMT+09:00 Szabolcs Nagy <nsz@port70.net>:
> * 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.
Thank you for letting me know!
--
Masanori Ogino
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
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
1 sibling, 1 reply; 6+ messages in thread
From: Rich Felker @ 2016-06-26 16:12 UTC (permalink / raw)
To: musl; +Cc: lowrisc-dev
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.
If gcc isn't planning to fix this, I think we should find a good
out-of-the-box workaround in libc-test. That would probably be either
a probe for gcc needing -P, or a filter to undo whatever mangling gcc
does without -P. It seems like a fairly trivial sed script could do
the latter.
Rich
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
2016-06-26 16:12 ` Rich Felker
@ 2016-06-26 22:51 ` Khem Raj
2016-06-27 0:57 ` Rich Felker
0 siblings, 1 reply; 6+ messages in thread
From: Khem Raj @ 2016-06-26 22:51 UTC (permalink / raw)
To: musl; +Cc: lowrisc-dev
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
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
>
> If gcc isn't planning to fix this, I think we should find a good
> out-of-the-box workaround in libc-test. That would probably be either
> a probe for gcc needing -P, or a filter to undo whatever mangling gcc
> does without -P. It seems like a fairly trivial sed script could do
> the latter.
>
> Rich
[-- Attachment #2: Type: text/html, Size: 1229 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4
2016-06-26 22:51 ` Khem Raj
@ 2016-06-27 0:57 ` Rich Felker
0 siblings, 0 replies; 6+ messages in thread
From: Rich Felker @ 2016-06-27 0:57 UTC (permalink / raw)
To: musl, lowrisc-dev
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-27 0:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-18 13:21 [GSoC2016] Weekly Report of Porting musl to RISC-V Project #4 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
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).