public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112367] wrong rounding of sum of floating-point constants
Date: Fri, 03 Nov 2023 11:21:26 +0000	[thread overview]
Message-ID: <bug-112367-4-VqrP9guzuv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112367-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Paul Zimmermann from comment #2)
> > Build a newer one on cfarm117?
> 
> it would be a waste of time, I guess people having access to an ARM machine
> with a recent version of gcc can confirm or say the issue is fixed.
> 

I don't think it's a waste of time, as you're often IIRC working on these
tests, so it would be useful to know. But I digress.

I also offer you access to an arm64 machine if you wish to have it.

> > Also, what CHOST?
> 
> sorry I'm not sure to understand. Here is the full gcc -v output:
> 

CHOST tells us ABI so I know what machine to check (also needed in general for
the report). I suppose I really wanted CTARGET.


> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/6/lto-wrapper
> Target: aarch64-linux-gnu

This is what I needed. Thanks.

  parent reply	other threads:[~2023-11-03 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 11:09 [Bug c/112367] New: " zimmerma+gcc at loria dot fr
2023-11-03 11:11 ` [Bug c/112367] " sjames at gcc dot gnu.org
2023-11-03 11:15 ` zimmerma+gcc at loria dot fr
2023-11-03 11:21 ` sjames at gcc dot gnu.org [this message]
2023-11-03 11:21 ` sjames at gcc dot gnu.org
2023-11-03 11:40 ` amonakov at gcc dot gnu.org
2023-11-04  5:48 ` [Bug middle-end/112367] " pinskia at gcc dot gnu.org
2023-11-06  8:59 ` [Bug middle-end/112367] wrong rounding of sum of floating-point constants with -frounding-math zimmerma+gcc at loria dot fr

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=bug-112367-4-VqrP9guzuv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).