public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/55336] New: Feature request : message output format XML
@ 2012-11-15 8:05 clemens1509 at web dot de
2012-11-15 8:08 ` [Bug middle-end/55336] " pinskia at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: clemens1509 at web dot de @ 2012-11-15 8:05 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55336
Bug #: 55336
Summary: Feature request : message output format XML
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: clemens1509@web.de
Every compiler has its own error output format. It would be better for IDE's if
all would have the same error message output syntax.
Benefits:
- easier parsing for all developmetn environments
- compount errors can be handelt together like
Exanmple:
<error index=0 id=W0004711> !# index starting from zero
<text file=myfile.cpp line=12345>wrong number of arguments in function
xyz</text>
<text file=myfile2 line=54321>error occurs at this position</text>
</error>
In this example you can see how it is possible to connect errors together.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/55336] Feature request : message output format XML
2012-11-15 8:05 [Bug c/55336] New: Feature request : message output format XML clemens1509 at web dot de
@ 2012-11-15 8:08 ` pinskia at gcc dot gnu.org
2012-11-15 8:25 ` clemens1509 at web dot de
2012-11-15 10:39 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-11-15 8:08 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55336
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |middle-end
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-11-15 08:08:31 UTC ---
I doubt this will be implemented. The format for GCC's warning and errors are
simple to parse as of right now. In fact GCC will never have an id to the
warning/error message.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/55336] Feature request : message output format XML
2012-11-15 8:05 [Bug c/55336] New: Feature request : message output format XML clemens1509 at web dot de
2012-11-15 8:08 ` [Bug middle-end/55336] " pinskia at gcc dot gnu.org
@ 2012-11-15 8:25 ` clemens1509 at web dot de
2012-11-15 10:39 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: clemens1509 at web dot de @ 2012-11-15 8:25 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55336
--- Comment #2 from Clemens <clemens1509 at web dot de> 2012-11-15 08:24:41 UTC ---
(In reply to comment #1)
> I doubt this will be implemented. The format for GCC's warning and errors are
> simple to parse as of right now. In fact GCC will never have an id to the
> warning/error message.
The idea is not to make parsing more simple, just make parsing common to *all*
compiler.
The second idea is that error messages could be connected together. This is
right now only possible of parser know the semantic of an msg. It can no be
determined from message format itself.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/55336] Feature request : message output format XML
2012-11-15 8:05 [Bug c/55336] New: Feature request : message output format XML clemens1509 at web dot de
2012-11-15 8:08 ` [Bug middle-end/55336] " pinskia at gcc dot gnu.org
2012-11-15 8:25 ` clemens1509 at web dot de
@ 2012-11-15 10:39 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: manu at gcc dot gnu.org @ 2012-11-15 10:39 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55336
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |DUPLICATE
--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-11-15 10:39:35 UTC ---
Hi Clemens,
What IDE? I already implemented a prototype patch for this in PR 19165, and
there was zero interest from any IDE people. I honestly believe that if you
don't have interested people with the access and the time to integrate this
into a major IDE (Eclipse, Kdevelop, Emacs), then it will be a wasted effort.
In any case, nobody currently working on GCC has the time or the interest to
work on such a feature, so you would need to start contributing to GCC or hire
someone to implement it.
*** This bug has been marked as a duplicate of bug 19165 ***
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-11-15 10:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-15 8:05 [Bug c/55336] New: Feature request : message output format XML clemens1509 at web dot de
2012-11-15 8:08 ` [Bug middle-end/55336] " pinskia at gcc dot gnu.org
2012-11-15 8:25 ` clemens1509 at web dot de
2012-11-15 10:39 ` manu at gcc dot gnu.org
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).