From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 23EAF3857BB0; Wed, 10 Jan 2024 11:18:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23EAF3857BB0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704885506; bh=+CXhWqVzy3NUay5sHfPAkiOhDCbE/hZhyinQqS3pI8k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gHczI14BatVKndJidxbgUrHtyNFSWStevuzgLvkh0/fm1ojWYpORMdKTWYgq3iURM crBzc/1bZCTRa0VdZM65KwmJcbLufBmFEspZAoDZNqv+u8lWjpXMhpGnUD5DLdCZww fAfhwlGGJHLdSdeQRAZjuGBzSIoF/jN/MOhh0Sqo= From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113156] [11/12/13/14 Regression] AVR build broken due to ICE while compiling libgcc, started with r14-6201-gf0a90c7d7333fc Date: Wed, 10 Jan 2024 11:18:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build, ice-checking, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D113156 --- Comment #10 from Georg-Johann Lay --- -mdouble and -mlong-double are more complicated than other options because = they depend on each other in way that (to my knowledge) cannot be described by option properties. For example, in -mdouble=3D64 -mlong-double=3D32 the second option will trigger -mdouble=3D32 in order to maintain double <= =3D long double. This logic is implemented in avr-common.cc::avr_handle_option(), and maybe that's the reason "Save" is needed? Anyway, when the actions of avr_handle_option are changed by some attribue handling, then the result will be wong code. For example, when the above options, for whatever reasons, would lead to double=3D64 longdouble=3D32 at= some point, wrong code will be generated.=