From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fweimer@redhat.com>
Received: from us-smtp-delivery-124.mimecast.com
 (us-smtp-delivery-124.mimecast.com [170.10.129.124])
 by sourceware.org (Postfix) with ESMTPS id AAFC43858D37
 for <gcc-help@gcc.gnu.org>; Wed,  2 Mar 2022 10:22:50 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AAFC43858D37
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-583-p7wtpD7CMeGW81ySF0mZOQ-1; Wed, 02 Mar 2022 05:22:49 -0500
X-MC-Unique: p7wtpD7CMeGW81ySF0mZOQ-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com
 [10.5.11.16])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1E8F2801AAD;
 Wed,  2 Mar 2022 10:22:48 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.39.192.88])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id 2DABD7B6F4;
 Wed,  2 Mar 2022 10:22:46 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: Reinoud Koornstra via Gcc-help <gcc-help@gcc.gnu.org>
Cc: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Subject: Re: Fortify_source and stack-protector-strong
References: <CAAA5faFWb6xz2mJ0LzRTxRHARq9vdmF+4bChWWEZCuW+uCNB4Q@mail.gmail.com>
Date: Wed, 02 Mar 2022 11:22:45 +0100
In-Reply-To: <CAAA5faFWb6xz2mJ0LzRTxRHARq9vdmF+4bChWWEZCuW+uCNB4Q@mail.gmail.com>
 (Reinoud Koornstra via Gcc-help's message of "Tue, 1 Mar 2022 15:23:08
 -0800")
Message-ID: <87o82ok616.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gcc-help@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-help mailing list <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2022 10:22:51 -0000

* Reinoud Koornstra via Gcc-help:

> Is it possible to compile with -stack-protector-strong and
> FORTIFY_SOURCE=1 or =2?  Or should both be used exclusively from
> another? Both check for similar things.

They complement each other.  I think most distributions use both these
days (-fstack-protector-strong and -D_FORTIFY_SOURCE=2).

Thanks,
Florian