public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114993] ICE when using bpf-unknown-g++
Date: Wed, 08 May 2024 19:18:47 +0000	[thread overview]
Message-ID: <bug-114993-4-sMf0lLvoih@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114993-4@http.gcc.gnu.org/bugzilla/>

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

Marc Poulhiès <dkm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |jemarch at gcc dot gnu.org

--- Comment #2 from Marc Poulhiès <dkm at gcc dot gnu.org> ---
After discussing on IRC, C++ (or anything != C) is not supported by BPF.
The fix is probably to display an error when using anything else than the C FE.

The Rust FE gives another error:
https://c.godbolt.org/z/TeWa3cshd

bpf-unknown-gcc: warning: <source>: linker input file unused because linking
not done

Not sure why it does not even use crab1 in this case.

  parent reply	other threads:[~2024-05-08 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 19:10 [Bug target/114993] New: " dkm at gcc dot gnu.org
2024-05-08 19:16 ` [Bug target/114993] " dkm at gcc dot gnu.org
2024-05-08 19:18 ` dkm at gcc dot gnu.org [this message]
2024-05-12  6:39 ` dkm 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-114993-4-sMf0lLvoih@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).