From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F25413858412; Thu, 2 Feb 2023 08:22:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F25413858412 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675326134; bh=Mwl4P+WGIhkveYY+jiXGEkIlxAtj1ffraKE4PQ9QxlM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lz0wI8bvbWN3I2nccdj90PVYvjaXMijuAD/pjReYAVeRPuJUHA2ZPfz9FSgjJHqg6 IuoP3X7jyfgxXC+DOVC5ImkyyIIRrMN6SSXJkMJIAW5C6GfqHbWYECK6xM/pVFaoro qoqpTwWGFRJ08gXesiGkhRkO74v2uh2uHiXMRJh8= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108623] We need to grow the precision field in tree_type_common for PowerPC Date: Thu, 02 Feb 2023 08:22:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108623 --- Comment #9 from rguenther at suse dot de --- On Wed, 1 Feb 2023, meissner at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108623 >=20 > Michael Meissner changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > Last reconfirmed| |2023-02-01 > Ever confirmed|0 |1 > Status|UNCONFIRMED |NEW >=20 > --- Comment #6 from Michael Meissner --- > Yes I agree we want an assetion in sext_hwi as well. >=20 > Richard, are you going to submit the patch, or did you want me to do it (= along > with the assertion)? Please you do it, as far as I understand Richard S. no further adjustment is necessary but we could simplify some code after the change(?)=