public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67795] Wrong code generated for conditional expression with cast Date: Thu, 01 Oct 2015 12:57:00 -0000 [thread overview] Message-ID: <bug-67795-4-9rT2GsTVbo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67795-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 Marc Glisse <glisse at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Version|5.2.0 |unknown Resolution|INVALID |--- --- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> --- Hmm, with the static_cast, the front-end produces: <<cleanup_point return <retval> = (struct string_view &) (struct string_view *) NON_LVALUE_EXPR <(struct string_view &) &(n != 0 ? std::experimental::fundamentals_v1::basic_string_view<char>::remove_prefix ((struct string_view *) s, n);, *s; : *s)>>>; while without it, I get: <<cleanup_point return <retval> = (struct string_view &) (n != 0 ? std::experimental::fundamentals_v1::basic_string_view<char>::remove_prefix ((struct string_view *) s, n);, (struct string_view *) s; : (struct string_view *) s)>>; I also find it fishy. (note that you need -O2 or more for the warning)
next prev parent reply other threads:[~2015-10-01 12:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-01 10:52 [Bug c++/67795] New: " frankhb1989 at gmail dot com 2015-10-01 11:14 ` [Bug c++/67795] " trippels at gcc dot gnu.org 2015-10-01 12:28 ` frankhb1989 at gmail dot com 2015-10-01 12:42 ` frankhb1989 at gmail dot com 2015-10-01 12:52 ` rguenth at gcc dot gnu.org 2015-10-01 12:56 ` frankhb1989 at gmail dot com 2015-10-01 12:57 ` glisse at gcc dot gnu.org [this message] 2015-10-01 13:06 ` frankhb1989 at gmail dot com 2015-10-01 13:09 ` frankhb1989 at gmail dot com 2015-10-01 13:13 ` frankhb1989 at gmail dot com 2021-10-11 1:50 ` pinskia at gcc dot gnu.org 2021-12-09 9:12 ` marxin at gcc dot gnu.org 2022-02-01 15:56 ` marxin 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-67795-4-9rT2GsTVbo@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).