From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Show all warnings and errors
Date: Tue, 01 Jan 2019 20:47:00 -0000 [thread overview]
Message-ID: <CABgWrqq2Y8O_ZcFMmLvjTrrR1+YD6nmDz5vSsFnnSHeAd70v7w@mail.gmail.com> (raw)
In-Reply-To: <baaf31b0-9630-f52b-601f-0b9f426a40e6@bothner.com>
I tried out the --max-error=NNN option and it doesn't seem to have
changed how the output comes out.
Here's what I see:
https://gist.github.com/duncanmak/38f451c9f26ba0000be38d0bd304313b
On Mon, Dec 31, 2018 at 9:12 PM Per Bothner <per@bothner.com> wrote:
>
> On 12/31/18 3:18 PM, Duncan Mak wrote:
>
> > I've been porting some code to Kawa lately, but I still have a lot of
> > work left to do.
>
> Cool.
>
> > Right now, when I load in the code, Kawa prints out a list of "warning
> > - no declaration seen for XXX", and it ends with:
> >
> > note - skipped 0 errors, 164 warnings, 0 notes
> >
> > Is there a switch to force it to print out all the warnings? Right
> > now, i'm getting only the top 20.
>
> There is now :-)
>
> --max-errors=NNN
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
--
Duncan.
next prev parent reply other threads:[~2019-01-01 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 23:18 Duncan Mak
2019-01-01 2:12 ` Per Bothner
2019-01-01 2:33 ` Duncan Mak
2019-01-01 2:42 ` Per Bothner
2019-01-01 20:47 ` Duncan Mak [this message]
2019-01-01 20:58 ` Per Bothner
2019-01-01 21:16 ` Duncan Mak
2019-01-01 21:24 ` Per Bothner
2019-01-01 21:31 ` Duncan Mak
2019-01-01 21:42 ` Per Bothner
2019-01-01 22:08 ` Duncan Mak
2022-09-18 3:03 ` Duncan Mak
2022-09-18 19:11 ` Per Bothner
2022-09-18 22:06 ` Duncan Mak
2022-09-19 10:48 ` Per Bothner
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=CABgWrqq2Y8O_ZcFMmLvjTrrR1+YD6nmDz5vSsFnnSHeAd70v7w@mail.gmail.com \
--to=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).