This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: _FORTIFY_SOURCE for std::vector

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Florian Weimer <fweimer at redhat dot com>, libstdc++ at gcc dot gnu dot org, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 01 Jun 2012 15:39:12 +0200
Subject: Re: _FORTIFY_SOURCE for std::vector
References: <4FC8A0DE.7030104@redhat.com> <4FC8AA97.2010909@oracle.com> <4FC8BB52.7030600@redhat.com> <4FC8BEFF.1050007@oracle.com> <20120601133445.GK24904@tucnak.redhat.com>

On 06/01/2012 03:34 PM, Jakub Jelinek wrote:

The standard -D_FORTIFY_SOURCE failure is __chk_fail (), so IMNSHO if this is presented as _FORTIFY_SOURCE check, it should call that and not some other function.

I understand. I don't know much about -D_FORTIFY_SOURCE, honestly. I hope the diagnostics provided by __chk_fail is good enough. And well, then we really do have to explain in a comment where __chk_fail is coming from ;)

Paolo.

Follow-Ups:
- Re: _FORTIFY_SOURCE for std::vector
  - From: Jakub Jelinek

References:
- _FORTIFY_SOURCE for std::vector
  - From: Florian Weimer
- Re: _FORTIFY_SOURCE for std::vector
  - From: Paolo Carlini
- Re: _FORTIFY_SOURCE for std::vector
  - From: Florian Weimer
- Re: _FORTIFY_SOURCE for std::vector
  - From: Paolo Carlini
- Re: _FORTIFY_SOURCE for std::vector
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]