From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D02C73858C83; Wed, 11 Jan 2023 23:06:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D02C73858C83
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1673478411;
	bh=5EABGv9gitXICxMr6uZtpXDaGHN0D4UztY8pQ4ANOv0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ULrtsfvrcQ25BcNEwfcXEVFKD1HrZqZAD48UhegHONNks0qvbAOrdi9Ku1w5bV0Zf
	 UD4CaifsHHh/6Pi6NqJsDOO1VwkcPEW+Y0n6xIFUsdUtgtpfl14DYDHbGd4gTKTk75
	 g2GJORS+3qwpxYEbLEvr1ceXiEbTocKmwwX0C1Ys=
From: "already5chosen at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/108279] Improved speed for float128 routines
Date: Wed, 11 Jan 2023 23:06:49 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: already5chosen at yahoo dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108279-4-76ArcwRdVU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108279-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108279-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108279

--- Comment #5 from Michael_S <already5chosen at yahoo dot com> ---
Hi Thomas
Are you in or out?

If you are still in, I can use your help on several issues.

1. Torture.=20
See if Invalid Operand exception raised properly now. Also if there are sti=
ll
remaining problems with NaN.

2. Run my correction tests on as many non-AMD64 targets as you can. Prefera=
bly,
with 100,000,000 iterations, but on weaker HW 10,000,000 will do.

3. Run my speed tests (tests/matmulq/mm_speed_ma) on more diverse set of AM=
D64
computers than I did.
Of special interest are
- AMD Zen3 on Linux running on bare metal
- Intel Skylake, SkylakeX, Tiger/Rocket Lake and Alder Lake on Linux runnin=
g on
bare metal
I realize that doing speed tests is not nearly as simple as correctness tes=
ts.
We need non-busy (preferably almost idle) machines that have stable CPU clo=
ck
rate. It's not easy to find machines like that nowadays. But, may be, you c=
an
find at least some from the list.

4. Run my speed tests on as many non-obsolete ARM64 computers as you can fi=
nd.
Well, probably a wishful thinking on my part.


Also off topic but of interest: postprocessed source of matmul_r16.c=