https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96032
--- Comment #12 from Kamil Dudka ---
I confirm that sarif-replay is available on f42+ and it seems to work as
expected. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96032
--- Comment #8 from Kamil Dudka ---
Where can one get the sarif-replay tool? It does not seem to be included in
gcc-latest.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117667
Kamil Dudka changed:
What|Removed |Added
CC||kdudka at redhat dot com
See Al
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117667
Bug ID: 117667
Summary: -flto=auto prevents -fanalyzer from reporting any
warnings on a build of systemd
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #34 from Kamil Dudka ---
(In reply to David Malcolm from comment #33)
> Note that the "2.2-prerelease" stuff does almost nothing at this stage and
> is experimental; you should probably leave "version" unset so that it uses
> the def
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #32 from Kamil Dudka ---
Thanks for the update! I confirm that the man page is readable now and that
the use of -fdiagnostics-set-output= eliminated the duplicated output without
the ugly workaround. I have also tried sarif:version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #27 from Kamil Dudka ---
Sounds good, looking forward to try out a new COPR build!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #24 from Kamil Dudka ---
(In reply to David Malcolm from comment #21)
> (In reply to David Malcolm from comment #20)
> > How about another option
> > -fdiagnostics-set-output=
> > that would work like
> > -fdiagnostics-add-outpu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #19 from Kamil Dudka ---
Thank you for working on this! I really like the gcc-latest COPR, which makes
it easy to test the changes. I spotted that man pages installed by gcc-latest
are broken but that is a cosmetic issue.
I have h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #16 from Kamil Dudka ---
(In reply to David Malcolm from comment #15)
> (In reply to Kamil Dudka from comment #14)
> > 1. Will `file=` work with absolute paths?
>
> Yes. There might be some issues with expressing paths/filenames co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #14 from Kamil Dudka ---
I think that the above described interface looks reasonable. A few questions:
1. Will `file=` work with absolute paths?
2. If a file with the specified name exists, will it be overwritten?
3. Will the file a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #7 from Kamil Dudka ---
(In reply to Eric Gallager from comment #6)
> Yeah, in particular, I'd want to send text to stdout while also sending
> SARIF to a file that shares the input file's name, except with the .sarif
> extension. (i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104308
Kamil Dudka changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104308
Kamil Dudka changed:
What|Removed |Added
CC||kdudka at redhat dot com
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104308
Bug ID: 104308
Summary: no location info provided for
[-Wanalyzer-use-of-uninitialized-value] warnings
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity:
15 matches
Mail list logo
