public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111908] New: Port CheriBSD-specific compiler warnings to GCC
Date: Sat, 21 Oct 2023 12:06:57 +0000	[thread overview]
Message-ID: <bug-111908-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111908
           Summary: Port CheriBSD-specific compiler warnings to GCC
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: build, diagnostic
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: egallager at gcc dot gnu.org
                CC: jrtc27 at jrtc27 dot com
            Blocks: 44756, 87403
  Target Milestone: ---
            Target: CheriBSD

The GCC compile farm has a CheriBSD machine, cfarm240, where the C/C++ memory
rules are stricter than normal. CheriBSD modifications to C/C++ are described
in the CHERI C/C++ Programming Guide:
https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-947.pdf
The document outlines a number of warnings that their compiler has for code
that will break on CheriBSD, specifically:

- -Wcheri-prototypes (kinda like -Wstrict-prototypes)
- -Wcheri-capability-misuse (kinda like -Wint-to-pointer-cast and
-Wpointer-to-int-cast; says something like "warning: cast from provenance-free
integer type to pointer type will give pointer that can not be dereferenced")
- -Wcheri-provenance (says something like "warning: binary expression on
capability types; it is not clear which should be used as the source of
provenance")

Note that some of these warnings will show up in a build of GCC itself, and
will cause the build to fail if configured with --enable-werror
--enable-werror-always.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44756
[Bug 44756] [meta-bug] --enable-werror-always issues
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning

             reply	other threads:[~2023-10-21 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 12:06 egallager at gcc dot gnu.org [this message]
2023-10-21 21:17 ` [Bug target/111908] " jrtc27 at jrtc27 dot com
2023-10-23  9:58 ` acoplan at gcc dot gnu.org
2023-10-24  8:22 ` egallager at gcc dot gnu.org
2023-10-24  9:58 ` acoplan 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-111908-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).