public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Anyone using FTensor to test GCC (or otherwise)?
@ 2023-02-14 23:20 Gerald Pfeifer
  2023-02-15  4:09 ` NightStrike
  0 siblings, 1 reply; 3+ messages in thread
From: Gerald Pfeifer @ 2023-02-14 23:20 UTC (permalink / raw)
  To: gcc

From previous times we have FTensor
  https://gcc.gnu.org/testing/testing-ftensor.html
documented as one of the ways to test GCC.

Alas http://www.wlandry.net/Projects/FTensor has been down for a while, 
and there does not appear to be a new location?


Is anyone actually still using FTensor to test GCC (or otherwise)?

I'm wondering whether to simply delete that page...

Gerald


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Anyone using FTensor to test GCC (or otherwise)?
  2023-02-14 23:20 Anyone using FTensor to test GCC (or otherwise)? Gerald Pfeifer
@ 2023-02-15  4:09 ` NightStrike
  2023-02-17  1:22   ` [wwwdocs] testing: Tweak the link to upstream FTensor (was: Anyone using FTensor to test GCC (or otherwise)?) Gerald Pfeifer
  0 siblings, 1 reply; 3+ messages in thread
From: NightStrike @ 2023-02-15  4:09 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc

On Tue, Feb 14, 2023 at 6:20 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Alas http://www.wlandry.net/Projects/FTensor has been down for a while,
> and there does not appear to be a new location?

https://wlandry.net/Projects/FTensor/ works

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [wwwdocs] testing: Tweak the link to upstream FTensor (was: Anyone using FTensor to test GCC (or otherwise)?)
  2023-02-15  4:09 ` NightStrike
@ 2023-02-17  1:22   ` Gerald Pfeifer
  0 siblings, 0 replies; 3+ messages in thread
From: Gerald Pfeifer @ 2023-02-17  1:22 UTC (permalink / raw)
  To: NightStrike, gcc-patches; +Cc: gcc

On Tue, 14 Feb 2023, NightStrike wrote:
>> Alas http://www.wlandry.net/Projects/FTensor has been down for a while,
>> and there does not appear to be a new location?
> https://wlandry.net/Projects/FTensor/ works

Ah, indeed. Thank you! Somehow that must have been the one combination I 
did not try.

I pushed the little patch below.

Gerald

commit b74309c36e59105ef0d8e0d91a85a5bfa884e175
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Feb 17 02:19:19 2023 +0100

    Tweak the link to upstream FTensor.

diff --git a/htdocs/testing/testing-ftensor.html b/htdocs/testing/testing-ftensor.html
index 2e67b4d8..7b1f4675 100644
--- a/htdocs/testing/testing-ftensor.html
+++ b/htdocs/testing/testing-ftensor.html
@@ -11,7 +11,7 @@
 <h1>FTensor build and test guide</h1>
 
 <p>This page is a guide to running the testing and timing programs for the
-<a href="http://www.wlandry.net/Projects/FTensor">FTensor</a>
+<a href="https://wlandry.net/Projects/FTensor">FTensor</a>
 tensor class library as part of GCC integration testing.</p>
 
 <h2>Resource usage</h2>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-02-17  1:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-14 23:20 Anyone using FTensor to test GCC (or otherwise)? Gerald Pfeifer
2023-02-15  4:09 ` NightStrike
2023-02-17  1:22   ` [wwwdocs] testing: Tweak the link to upstream FTensor (was: Anyone using FTensor to test GCC (or otherwise)?) Gerald Pfeifer

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).