public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94939] [9.2.1] invalid code generation in ternary op with static class member (undefined behaviour nearby?)
Date: Mon, 04 May 2020 06:58:43 +0000	[thread overview]
Message-ID: <bug-94939-4-fVGym6FzQR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94939-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94939

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-05-04

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I would guess the type_safe libraries doing for
type_safe::get(static_cast<const Strongtypedef&>(*this)) is "wrong" (whatever
type_safe is guaranteeing).

Please provide a complete preprocessed testcase that can be compiled.

  parent reply	other threads:[~2020-05-04  6:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  6:49 [Bug c++/94939] New: " tobias.pankrath@ssw-trading.com
2020-05-04  6:50 ` [Bug c++/94939] " tobias.pankrath@ssw-trading.com
2020-05-04  6:58 ` rguenth at gcc dot gnu.org [this message]
2020-05-04  7:14 ` tobias.pankrath@ssw-trading.com
2021-07-18 22:44 ` pinskia at gcc dot gnu.org
2021-07-18 22:44 ` pinskia 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-94939-4-fVGym6FzQR@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: link
Be 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).