public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100629] Regression from 10 symbol mismatch between class definition and use with/without optimization
Date: Mon, 17 May 2021 18:15:30 +0000 [thread overview]
Message-ID: <bug-100629-4-CCYw3Go5dl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100629-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100629
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to James McKelvey from comment #10)
> Created attachment 50824 [details]
> Preprocessed source for main
This is header_edit.cc right?
I don't see any definition of the missing constructor here. This one:
BreakPattern(const pdstring& value,
const ConflateIntegerScalarValue& minimum,
const ConflateIntegerScalarValue& maximum,
const ComplementEnum& a_complement);
next prev parent reply other threads:[~2021-05-17 18:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 0:06 [Bug c++/100629] New: Regression from 10 symbol mismatch between class definition and use with optimization mckelvey at maskull dot com
2021-05-17 5:54 ` [Bug c++/100629] " mckelvey at maskull dot com
2021-05-17 5:59 ` mckelvey at maskull dot com
2021-05-17 7:00 ` pinskia at gcc dot gnu.org
2021-05-17 7:00 ` pinskia at gcc dot gnu.org
2021-05-17 7:01 ` pinskia at gcc dot gnu.org
2021-05-17 7:08 ` pinskia at gcc dot gnu.org
2021-05-17 9:36 ` redi at gcc dot gnu.org
2021-05-17 9:40 ` redi at gcc dot gnu.org
2021-05-17 16:32 ` mckelvey at maskull dot com
2021-05-17 16:34 ` mckelvey at maskull dot com
2021-05-17 16:57 ` [Bug c++/100629] Regression from 10 symbol mismatch between class definition and use with/without optimization mckelvey at maskull dot com
2021-05-17 16:58 ` mckelvey at maskull dot com
2021-05-17 17:04 ` mckelvey at maskull dot com
2021-05-17 18:15 ` redi at gcc dot gnu.org [this message]
2021-05-17 18:26 ` mckelvey at maskull dot com
2021-05-17 18:27 ` mckelvey at maskull dot com
2021-05-17 18:44 ` mckelvey at maskull dot com
2021-05-17 19:51 ` mckelvey at maskull dot com
2021-05-17 20:24 ` redi at gcc dot gnu.org
2021-05-17 20:34 ` redi at gcc dot gnu.org
2021-05-17 20:37 ` redi at gcc dot gnu.org
2021-05-17 20:53 ` redi at gcc dot gnu.org
2021-05-17 21:05 ` redi at gcc dot gnu.org
2021-05-17 21:36 ` mckelvey at maskull dot com
2021-05-17 22:02 ` redi at gcc dot gnu.org
2021-05-17 22:06 ` redi at gcc dot gnu.org
2021-05-17 22:29 ` redi at gcc dot gnu.org
2021-08-12 0:52 ` 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-100629-4-CCYw3Go5dl@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).