From: Michel <tatoute@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: errors message groups id?
Date: Fri, 11 Nov 2022 12:39:43 +0100 [thread overview]
Message-ID: <CAAy5hTnSf-fnCtaRgPnuFGgj_H93de495zFyeJ=cysPweUb6Ww@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Hello all,
GCC error/warning messages often provide a lot of extra information, which
is great.
It is done on a multiline way, like in:
foo.h:123:22: <context>
... etc
bar.h:234:12: error: <some error>
qwr.h:456:8: <additional context information / possible diagnostics>
.. etc
Nevertheless this has some drawbacks:
- Parallel compilation can mess up mixin lines from sep compilations
- Often one may want to reorder or deduplicate or archive errors, but
associated context lines are not attached to the main error line
Is there a compile option to ask GCC to emit some uuid with every
errors/context lines, so that an automated system may group them and manage
them at once? something like this:
foo.h:123:22:uuid1: <context>
... etc
bar.h:234:12:uuid1: error: <some error>
qwr.h:456:8:uuid1: <additional context information / possible diagnostics>
.. etc
Seems quite an easy feature to support, if it does not exist already.
Regards.
reply other threads:[~2022-11-11 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAy5hTnSf-fnCtaRgPnuFGgj_H93de495zFyeJ=cysPweUb6Ww@mail.gmail.com' \
--to=tatoute@gmail.com \
--cc=gcc-help@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).