public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview] Message-ID: <bug-113156-4-V7CJVN2hf6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113156-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113156 --- Comment #10 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- -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=64 -mlong-double=32 the second option will trigger -mdouble=32 in order to maintain double <= 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=64 longdouble=32 at some point, wrong code will be generated.
next prev parent reply other threads:[~2024-01-10 11:18 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-27 9:03 [Bug target/113156] New: " dimitar at gcc dot gnu.org 2023-12-27 9:11 ` [Bug target/113156] " pinskia at gcc dot gnu.org 2023-12-27 9:14 ` pinskia at gcc dot gnu.org 2024-01-04 22:04 ` paulbendixen at gmail dot com 2024-01-08 14:10 ` [Bug target/113156] [14 Regression] " rguenth at gcc dot gnu.org 2024-01-10 5:08 ` pinskia at gcc dot gnu.org 2024-01-10 5:11 ` pinskia at gcc dot gnu.org 2024-01-10 5:12 ` [Bug target/113156] [11/12/13/14 " pinskia at gcc dot gnu.org 2024-01-10 5:22 ` pinskia at gcc dot gnu.org 2024-01-10 9:18 ` gjl at gcc dot gnu.org 2024-01-10 9:23 ` pinskia at gcc dot gnu.org 2024-01-10 11:18 ` gjl at gcc dot gnu.org [this message] 2024-01-11 0:13 ` pinskia at gcc dot gnu.org 2024-01-15 9:42 ` cvs-commit at gcc dot gnu.org 2024-01-15 11:43 ` cvs-commit at gcc dot gnu.org 2024-01-15 11:49 ` cvs-commit at gcc dot gnu.org 2024-01-15 13:26 ` gjl at gcc dot gnu.org 2024-01-16 22:44 ` pinskia at gcc dot gnu.org 2024-01-17 8:29 ` gjl at gcc dot gnu.org
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-113156-4-V7CJVN2hf6@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: linkBe 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).