From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <segher@kernel.crashing.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
 by sourceware.org (Postfix) with ESMTP id 95AAB3858D3C
 for <gcc-help@gcc.gnu.org>; Mon, 22 Aug 2022 23:02:58 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 95AAB3858D3C
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=kernel.crashing.org
Authentication-Results: sourceware.org;
 spf=pass smtp.mailfrom=kernel.crashing.org
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])
 by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 27MN1reF025700;
 Mon, 22 Aug 2022 18:01:53 -0500
Received: (from segher@localhost)
 by gate.crashing.org (8.14.1/8.14.1/Submit) id 27MN1rVW025699;
 Mon, 22 Aug 2022 18:01:53 -0500
X-Authentication-Warning: gate.crashing.org: segher set sender to
 segher@kernel.crashing.org using -f
Date: Mon, 22 Aug 2022 18:01:53 -0500
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andrea Bocci <andrea.bocci@cern.ch>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Warn about conversion from floating point to integers
Message-ID: <20220822230153.GS25951@gate.crashing.org>
References: <CAAK6D=7L4J3o6_WutEKvTt2WhJNXCfywz-1_0mErboywbRp2Hw@mail.gmail.com>
 <20220822173203.GP25951@gate.crashing.org>
 <CAAK6D=6j0J2B1zzCU9z3mBvv_OUctOSOhHQc3Eu=Lnugd3-K=w@mail.gmail.com>
 <CAH6eHdSykrk0m6fMNFXpSTFmj4etRaYaAd4eYCwQBAyH+eX4oA@mail.gmail.com>
 <CAAK6D=4Bbub6w4pGOPPt_yX570TTgondB0G7oqVHUn4rW8fCtg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAK6D=4Bbub6w4pGOPPt_yX570TTgondB0G7oqVHUn4rW8fCtg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: gcc-help@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-help mailing list <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2022 23:03:00 -0000

Hi!

On Mon, Aug 22, 2022 at 09:48:01PM +0200, Andrea Bocci wrote:
> For the avoidance of doubt, "PR" in this context means "problem report"
> > i.e. bug report, not "pull request".

Yeah, sorry for the confusion.  We talk about PRs in GCC a lot, since
time immemorial, long before github existed anyway.  We do not use
github's workflows, they are not suitable for us.

> Ah... thanks for the clarification.
> That is definitely something I can do :-)

:-)  Thanks in advance!


Segher