public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110737] GCC: internal compiler error: Segmentation fault when processing __builtin_isinf and _Atomic long double together Date: Wed, 19 Jul 2023 22:29:28 +0000 [thread overview] Message-ID: <bug-110737-4-8ULtvsNMAr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110737 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- build_atomic_assign does not handle this in a reasonable fashion. Note there is code like : if (modifycode != NOP_EXPR) add_stmt (rhs); /* NOP_EXPR indicates it's a straight store of the RHS. Simply issue an atomic_store. */ if (modifycode == NOP_EXPR) { ... /* VAL is the value which was stored, return a COMPOUND_STMT of the statement and that value. */ return build2 (COMPOUND_EXPR, nonatomic_lhs_type, compound_stmt, val); } Which definitely could be improved too.
prev parent reply other threads:[~2023-07-19 22:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-19 8:19 [Bug c/110737] New: " 141242068 at smail dot nju.edu.cn 2023-07-19 9:38 ` [Bug c/110737] " rguenth at gcc dot gnu.org 2023-07-19 20:42 ` pinskia at gcc dot gnu.org 2023-07-19 21:00 ` pinskia at gcc dot gnu.org 2023-07-19 21:35 ` pinskia at gcc dot gnu.org 2023-07-19 22:29 ` pinskia at gcc dot gnu.org [this message]
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-110737-4-8ULtvsNMAr@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).