From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2F24E38582B3; Wed, 10 Jan 2024 09:18:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2F24E38582B3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704878282; bh=FyzIMuigqN8kEezpRWo3QyE0YJvImkoBztPc2izCLtM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SYNowyQBQnTRUrztz90LFgPymOWuuViDLsNYuHFe0us7vApKE53IVqhlcx6JAQrPu c8nh9Wzccrmmkwy6XP7Qf8zEU6jRi4CPQfn0HdwAsND6rl4QdmPFmgK7azdMNxMGpI p7fR8F1YZjBZ6S4PCUFF6mqMdlpgbfkz3xOuPH7Y= 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 09:18:00 +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 #8 from Georg-Johann Lay --- Is there as comprehensible explanation when option property "Save" is neede= d? The internals just state > Build the cl_target_option structure to hold a copy of the option, > add the functions cl_target_option_save and cl_target_option_restore > to save and restore the options. Which explains what is does, but not when and why it is needed. For example, -mdouble=3D and -mlong-double=3D are multilib options, and not optimizatoin options, and they whould never change during a program. Why is "Save" needed for some multilib options and not for others? Isn't it even a bug to allow multilib options to be changed due to optimiza= tion flags? A code that uses -mdouble=3D32 in some places and -mdouble=3D64 is = others is bogus.=