From: Richard Biener <rguenther@suse.de>
To: Matthew Malcomson <matthew.malcomson@arm.com>
Cc: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH] Reduce floating-point difficulties in timevar.cc
Date: Fri, 21 Jul 2023 12:47:38 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2307211244430.12935@jbgna.fhfr.qr> (raw)
In-Reply-To: <ded23976-2873-45de-aebd-28839ec0ab82@AZ-NEU-EX03.Arm.com>
On Fri, 21 Jul 2023, Matthew Malcomson wrote:
> On some AArch64 bootstrapped builds, we were getting a flaky test
> because the floating point operations in `get_time` were being fused
> with the floating point operations in `timevar_accumulate`.
>
> This meant that the rounding behaviour of our multiplication with
> `ticks_to_msec` was different when used in `timer::start` and when
> performed in `timer::stop`. These extra inaccuracies led to the
> testcase `g++.dg/ext/timevar1.C` being flaky on some hardware.
>
> This change ensures those operations are not fused and hence stops the test
> being flaky on that particular machine. There is no expected change in the
> generated code.
> Bootstrap & regtest on AArch64 passes with no regressions.
I think this is undesriable. With fused you mean we use FMA?
I think you could use -ffp-contract=off for the TU instead.
Note you can't use __attribute__((noinline)) literally since the
host compiler might not support this.
Richard.
> gcc/ChangeLog:
>
> * timevar.cc (get_time): Make this noinline to avoid fusing
> behaviour and associated test flakyness.
>
>
> N.b. I didn't know who to include as reviewer -- guessed Richard Biener as the
> global reviewer that had the most contributions to this file and Richard
> Sandiford since I've asked him for reviews a lot in the past.
>
>
> ############### Attachment also inlined for ease of reply ###############
>
>
> diff --git a/gcc/timevar.cc b/gcc/timevar.cc
> index d695297aae7f6b2a6de01a37fe86c2a232338df0..5ea4ec259e114f31f611e7105cd102f4c9552d18 100644
> --- a/gcc/timevar.cc
> +++ b/gcc/timevar.cc
> @@ -212,6 +212,7 @@ timer::named_items::print (FILE *fp, const timevar_time_def *total)
> HAVE_WALL_TIME macros. */
>
> static void
> +__attribute__((noinline))
> get_time (struct timevar_time_def *now)
> {
> now->user = 0;
>
>
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2023-07-21 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 12:11 Matthew Malcomson
2023-07-21 12:47 ` Richard Biener [this message]
2023-07-21 13:11 ` Matthew Malcomson
2023-07-21 13:41 ` Richard Biener
2023-07-21 13:45 ` Xi Ruoyao
2023-07-21 13:58 ` Alexander Monakov
2023-07-21 15:11 ` Xi Ruoyao
2023-07-21 15:56 ` Alexander Monakov
2023-07-21 15:24 ` Matthew Malcomson
2023-08-03 13:38 ` [PATCH] mid-end: Use integral time intervals " Matthew Malcomson
2023-08-03 14:09 ` David Malcolm
2023-08-03 14:54 ` Matthew Malcomson
2023-08-03 15:34 ` David Malcolm
2023-08-04 6:44 ` Richard Biener
2023-08-04 9:41 ` Matthew Malcomson
2023-08-04 10:18 ` Richard Biener
2023-07-21 12:49 ` [PATCH] Reduce floating-point difficulties " Xi Ruoyao
2023-07-21 17:41 ` Andrew Pinski
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=nycvar.YFH.7.77.849.2307211244430.12935@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=matthew.malcomson@arm.com \
--cc=richard.sandiford@arm.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.
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).