public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105634] [9/10/11/12/13 Regression] ICE: Floating point exception in maybe_warn_class_memaccess
Date: Tue, 17 May 2022 19:01:19 +0000 [thread overview]
Message-ID: <bug-105634-4-5JvTc6y4rE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105634-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105634
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Target Milestone|--- |9.5
CC| |mpolacek at gcc dot gnu.org
Summary|ICE: Floating point |[9/10/11/12/13 Regression]
|exception in |ICE: Floating point
|maybe_warn_class_memaccess |exception in
| |maybe_warn_class_memaccess
Priority|P3 |P5
Keywords| |error-recovery
Last reconfirmed| |2022-05-17
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r249234:
commit c3684b7b86da9b6b01f6fb274227fc6401df053e
Author: Martin Sebor <msebor@redhat.com>
Date: Fri Jun 16 03:48:59 2017 +0000
PR c++/80560 - warn on undefined memory operations involving non-trivial
types
next prev parent reply other threads:[~2022-05-17 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:46 [Bug c++/105634] New: " gscfq@t-online.de
2022-05-17 19:01 ` mpolacek at gcc dot gnu.org [this message]
2022-05-17 19:05 ` [Bug c++/105634] [9/10/11/12/13 Regression] " mpolacek at gcc dot gnu.org
2022-05-18 14:33 ` cvs-commit at gcc dot gnu.org
2022-05-18 14:36 ` [Bug c++/105634] [9/10/11/12 " mpolacek at gcc dot gnu.org
2022-07-19 17:13 ` mpolacek at gcc dot gnu.org
2022-07-19 18:25 ` cvs-commit at gcc dot gnu.org
2022-07-19 18:26 ` [Bug c++/105634] [9/10/11 " mpolacek 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-105634-4-5JvTc6y4rE@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).