public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107284] Option properties Mask infrastructure can be extended with wide_int_bitmask
Date: Wed, 28 Dec 2022 10:45:48 +0000 [thread overview]
Message-ID: <bug-107284-4-kmHdIWborj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107284-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107284
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org
Status|ASSIGNED |NEW
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
So apparently it won't be so simple as cl_target_option is a GGC structure and
thus wide_int_bitmask needs to use GTY. However, I get the following errors:
/home/marxin/Programming/gcc/gcc/wide-int-bitmask.h:26: undefined type
`constexpr'
/home/marxin/Programming/gcc/gcc/wide-int-bitmask.h:26: undefined type
`constexpr'
/home/marxin/Programming/gcc/gcc/wide-int-bitmask.h:26: undefined type
`constexpr'
Just for the record, right now, there are 26 free bits available in
ix86_isa_flags2.
next prev parent reply other threads:[~2022-12-28 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 3:09 [Bug middle-end/107284] New: " crazylht at gmail dot com
2022-10-17 11:57 ` [Bug middle-end/107284] " marxin at gcc dot gnu.org
2022-12-28 10:45 ` marxin at gcc dot gnu.org [this message]
2022-12-28 11:41 ` 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-107284-4-kmHdIWborj@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).