https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #8 from ibuclaw at gcc dot gnu.org ---
Author: ibuclaw
Date: Wed Apr 24 14:17:34 2019
New Revision: 270545
URL: https://gcc.gnu.org/viewcvs?rev=270545&root=gcc&view=rev
Log:
libphobos: Skip curl tests if libcurl is not installed on th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #7 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #0)
>
> 2) if Curl fails to initialize, the test shouldn't get stuck
>
This part has been done in r268746.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #6 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #4)
>
> My i686-linux bootstraps are done through a couple of executable scripts in
> ~/hbin directory on x86_64-linux:
> for i in ~/hbin/*; do echo ===$i===; cat $i; do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #5 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #4)
>
> If the test doesn't fail if it fails to load libcurl (and doesn't get
> stuck), it is fine too.
> If it fails if it is missing, yeah, something like a tcl proced
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #4 from Jakub Jelinek ---
(In reply to Iain Buclaw from comment #3)
> (In reply to Jakub Jelinek from comment #0)
> > The reason I'm filing this is that there are multiple issues:
> >
> > 1) what I'm worried about most is that the ti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #3 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #0)
> The reason I'm filing this is that there are multiple issues:
>
> 1) what I'm worried about most is that the timeouts for tests don't work, it
> happens that some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #2 from Iain Buclaw ---
(In reply to Richard Biener from comment #1)
> I think I saw a duplicate somewhere - this is using real-time threads pinned
> to a single CPU but yield()ing in a spinning loop expecting to make progress.
I che
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
