From: Arthur Cohen <arthur.cohen@embecosm.com>
To: gcc-patches@gcc.gnu.org
Cc: gcc-rust@gcc.gnu.org, dmalcolm@redhat.com
Subject: Re: [PATCHSET] Add error metadata to diagnostics
Date: Thu, 7 Sep 2023 11:39:03 +0200 [thread overview]
Message-ID: <916699a9-9d4f-5f29-88fa-46ba92800555@embecosm.com> (raw)
In-Reply-To: <20230906135303.3643659-1-arthur.cohen@embecosm.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1026 bytes --]
Pushed to trunk this morning with Changelogs and SoB lines.
Thanks for the review David!
All the best,
Arthur
On 9/6/23 15:53, Arthur Cohen wrote:
> This short patchset from David Malcolm enables errors to contain extra
> metadata - this is particularly useful for the Rust frontend, which will
> rely on that implementation to emit standard Rust error codes [1].
>
> This series of patches is necessary for much of our more recent
> additions to the frontend, including the work of one of this year's GSoC
> student, Mahad Muhammad, who has spent a lot of time working on emitting
> these error codes from the Rust frontend for GCC.
>
> We will soon resume upstreaming patches from our development repository
> to the main GCC repository, in the hopes of distributing the Rust frontend
> as part of the GCC 14.1 release.
>
> [PATCH 1/2] diagnostics: add error_meta
> [PATCH 2/2] Experiment with adding an error code to an error
>
> Are these OK for trunk?
>
> Kindly,
>
> Arthur
>
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-09-07 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 13:53 Arthur Cohen
2023-09-06 13:53 ` [PATCH 1/2] diagnostics: add error_meta Arthur Cohen
2023-09-06 14:12 ` David Malcolm
2023-09-06 14:24 ` Arthur Cohen
2023-09-06 13:53 ` [PATCH 2/2] Experiment with adding an error code to an error Arthur Cohen
2023-09-06 14:19 ` David Malcolm
2023-09-07 9:39 ` Arthur Cohen [this message]
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=916699a9-9d4f-5f29-88fa-46ba92800555@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@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).