public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110783] bpf; make sure of V4 signed division/modulus instructions
Date: Mon, 24 Jul 2023 14:01:20 +0000	[thread overview]
Message-ID: <bug-110783-4-yQXW1CSM1p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110783-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jose E. Marchesi <jemarch@gcc.gnu.org>:

https://gcc.gnu.org/g:4be3919fb75e3d2a4d2bb80ba33c14e0973bc08f

commit r14-2749-g4be3919fb75e3d2a4d2bb80ba33c14e0973bc08f
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date:   Mon Jul 24 15:57:05 2023 +0200

    bpf: sdiv/smod are now part of BPF V4

    We used to support signed division and signed modulus instructions in
    the XBPF GCC-specific extensions to BPF.  However, BPF catched up by
    adding these instructions in the V4 of the ISA.

    This patch changes GCC in order to use sdiv/smod instructions when
    -mcpu=v4 or higher.  The testsuite and the manual have been updated
    accordingly.

    Tested in bpf-unknown-none.

    gcc/ChangeLog

            PR target/110783
            * config/bpf/bpf.opt: New command-line option -msdiv.
            * config/bpf/bpf.md: Conditionalize sdiv/smod on bpf_has_sdiv.
            * config/bpf/bpf.cc (bpf_option_override): Initialize
            bpf_has_sdiv.
            * doc/invoke.texi (eBPF Options): Document -msdiv.

    gcc/testsuite/ChangeLog

            PR target/110783
            * gcc.target/bpf/xbpf-sdiv-1.c: Renamed to sdiv-1.c
            * gcc.target/bpf/xbpf-smod-1.c: Renamed to smod-1.c
            * gcc.target/bpf/sdiv-1.c: Renamed from xbpf-sdiv-1.c, use
-mcpu=v4.
            * gcc.target/bpf/smod-1.c: Renamed from xbpf-smod-1.c, use
-mcpu=v4.
            * gcc.target/bpf/diag-sdiv.c: Use -mcpu=v3.
            * gcc.target/bpf/diag-smod.c: Likewise.

  parent reply	other threads:[~2023-07-24 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 23:44 [Bug target/110783] New: " jemarch at gcc dot gnu.org
2023-07-24 10:21 ` [Bug target/110783] " jemarch at gcc dot gnu.org
2023-07-24 14:01 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-24 14:03 ` jemarch 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-110783-4-yQXW1CSM1p@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).