public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin
Date: Sat, 15 Jan 2022 21:50:20 +0000	[thread overview]
Message-ID: <bug-104042-4-nnkOw4Yg7H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104042-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So I suspect they will fail if you default the linux compiler to
_FORTIFY_SOURCE=2 then too. (I thought there was a configure option to do that
or maybe Debian/Ubuntu has patches for it I forget).

  parent reply	other threads:[~2022-01-15 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 14:03 [Bug analyzer/104042] New: " fxcoudert at gcc dot gnu.org
2022-01-15 14:05 ` [Bug analyzer/104042] " fxcoudert at gcc dot gnu.org
2022-01-15 14:23 ` iains at gcc dot gnu.org
2022-01-15 14:24 ` iains at gcc dot gnu.org
2022-01-15 21:50 ` pinskia at gcc dot gnu.org [this message]
2023-08-19 21:29 ` fxcoudert at gcc dot gnu.org
2023-11-03 13:21 ` fxcoudert at gcc dot gnu.org
2024-04-01 13:27 ` cvs-commit at gcc dot gnu.org
2024-04-20 14:46 ` cvs-commit at gcc dot gnu.org
2024-04-28 14:43 ` cvs-commit at gcc dot gnu.org

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=bug-104042-4-nnkOw4Yg7H@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).