From: Kamil Dudka <kdudka@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] utimens: fix confusing arg type in internal func
Date: Sat, 10 Apr 2021 15:16:49 +0200 [thread overview]
Message-ID: <3139755.aV6nBDHxoP@nbkamil> (raw)
In-Reply-To: <4747830c-02e4-e049-0ab6-b61586f7c29b@cs.ucla.edu>
On Saturday, April 10, 2021 3:19:08 AM CEST Paul Eggert wrote:
> On 4/9/21 12:50 AM, Kamil Dudka wrote:
> > The warning[-Wstringop-overflow=] reports you refer to come from GCC
> > actually.
> Weird. The code being warned about has nothing to do with strings, and
> the only string operation in the entire module is strlen and it is
> compiled only on macOS.
I can see some regressions about stringop-overflow false positives in
upstream bugzilla. They could be related to these reports.
> And I don't get a warning from GCC or from Clang
> when I run it myself on the "unfixed" version.
This happens with a pre-release of gcc-11.
> I suspect Coverity is using GCC (or Clang?) in some odd way, so for now
> let's keep "Coverity" in the ChangeLog entry.
Definitely not. I am able to reproduce it with gcc-11.0.0-0.20.fc34 or
gcc-11.0.1-0.4.fc34 on a Fedora 34 VM where none of the other tools is
installed.
Kamil
next prev parent reply other threads:[~2021-04-10 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 0:30 [PATCH] utimens: fix confusing arg type in internal func Paul Eggert
2021-04-09 7:50 ` Kamil Dudka
2021-04-10 1:19 ` Paul Eggert
2021-04-10 13:16 ` Kamil Dudka [this message]
2021-04-10 20:42 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3139755.aV6nBDHxoP@nbkamil \
--to=kdudka@redhat.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).