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/110770] bpf: add pseudoc assembly dialect
Date: Fri, 21 Jul 2023 19:02:30 +0000	[thread overview]
Message-ID: <bug-110770-4-wIMatP0uPe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110770-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Cupertino Miranda <cupermir@gcc.gnu.org>:

https://gcc.gnu.org/g:77d0f9ec3809b4d2e32c36069b6b9239d301c030

commit r14-2720-g77d0f9ec3809b4d2e32c36069b6b9239d301c030
Author: Cupertino Miranda <cupertino.miranda@oracle.com>
Date:   Mon Jul 17 17:42:42 2023 +0100

    bpf: pseudo-c assembly dialect support

    New pseudo-c BPF assembly dialect already supported by clang and widely
    used in the linux kernel.

    gcc/ChangeLog:

            PR target/110770
            * config/bpf/bpf.opt: Added option -masm=<dialect>.
            * config/bpf/bpf-opts.h (enum bpf_asm_dialect): New type.
            * config/bpf/bpf.cc (bpf_print_register): New function.
            (bpf_print_register): Support pseudo-c syntax for registers.
            (bpf_print_operand_address): Likewise.
            * config/bpf/bpf.h (ASM_SPEC): handle -msasm.
            (ASSEMBLER_DIALECT): Define.
            * config/bpf/bpf.md: Added pseudo-c templates.
            * doc/invoke.texi (-masm=): New eBPF option item.

  reply	other threads:[~2023-07-21 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 18:53 [Bug target/110770] New: " cupertino.miranda at oracle dot com
2023-07-21 19:02 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-21 20:26 ` [Bug target/110770] " pinskia at gcc dot gnu.org
2023-08-17 17:16 ` 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-110770-4-wIMatP0uPe@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).