public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107284] New: Option properties Mask infrastructure can be extended with wide_int_bitmask
Date: Mon, 17 Oct 2022 03:09:05 +0000	[thread overview]
Message-ID: <bug-107284-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107284
           Summary: Option properties Mask infrastructure can be extended
                    with wide_int_bitmask
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: crazylht at gmail dot com
  Target Milestone: ---

For x86, as more and more ISAs are introduced, we're almost running out of
ix86_isa_flags2, a ix86_isa_flags3 needs to be introduced, that caused
maintainance difficulty since there're depenedence between bits in different
isa_flag(and several values used as same purpose for isa bit mask), it would be
nice if we can introduce wide_int_bit_mask in the
opth-gen.awk/opts-functions.awk ..etc, extend wide_int_bit_mask to 256 bits,
and overload bit set/shift in wide_int_bitmask.h. So the backend can be
released from maintain those "overloads" for mask bits.

             reply	other threads:[~2022-10-17  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  3:09 crazylht at gmail dot com [this message]
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
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@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).