From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
jakub@redhat.com, law@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: Analyzer committed to master (was Re: Analyzer status)
Date: Sat, 18 Jan 2020 17:02:00 -0000 [thread overview]
Message-ID: <ydd4kws7r7m.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <6aa093654d4ad80aa196e67b2aec97ef546d4ca4.camel@redhat.com> (David Malcolm's message of "Wed, 15 Jan 2020 15:29:33 -0500")
Hi David,
>> I'm seeing quite a number of failures on Solaris (both sparc and
>> x86),
>> but also some on 32-bit Linux/x86:
>>
>> Running target unix/-m32
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 610)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 611)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 615)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 616)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 657)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 658)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 662)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 663)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 705)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 706)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 710)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 711)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 753)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 754)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 758)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 759)
>> +FAIL: gcc.dg/analyzer/data-model-1.c (test for excess errors)
>
> Thanks, and sorry about this; I've filed this for myself as:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93281
> and have been investigating.
>
>> I'll file PRs for the Solaris ones once I get to it.
I've now filed PR analyzer/93316 for the rest; most of the errors there
also occur on at least one non-Solaris target.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2020-01-18 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 23:42 Analyzer status David Malcolm
2020-01-13 23:55 ` Jakub Jelinek
2020-01-14 1:29 ` Jakub Jelinek
2020-01-14 1:30 ` David Malcolm
2020-01-14 2:58 ` Jakub Jelinek
2020-01-14 4:52 ` David Malcolm
2020-01-14 8:24 ` [PATCH 1/2] hash-table.h: support non-zero empty values in empty_slow (v2) David Malcolm
2020-01-14 7:55 ` [PATCH 2/2] analyzer: add empty_zero_p for the various hash traits David Malcolm
2020-01-14 11:07 ` [PATCH 1/2] hash-table.h: support non-zero empty values in empty_slow (v2) Jakub Jelinek
2020-01-14 19:14 ` David Malcolm
2020-01-14 8:31 ` Analyzer status Richard Biener
2020-01-14 21:10 ` Analyzer committed to master (was Re: Analyzer status) David Malcolm
2020-01-15 12:37 ` Rainer Orth
2020-01-15 20:12 ` Dimitar Dimitrov
2020-01-15 20:29 ` Iain Sandoe
2020-01-15 20:53 ` David Malcolm
2020-01-16 6:43 ` [PATCH] analyzer: fix handling of negative byte offsets (PR 93281) David Malcolm
2020-01-16 7:39 ` Richard Biener
2020-01-16 8:56 ` Jakub Jelinek
2020-01-18 17:02 ` Rainer Orth [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=ydd4kws7r7m.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).