summaryrefslogtreecommitdiff
path: root/Porting/todo.pod
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2012-03-30 18:22:50 +0200
committerNicholas Clark <nick@ccl4.org>2012-04-24 10:51:55 +0200
commit2a930eeaa11a10dc2ffcb200563ba5641ac15840 (patch)
tree04246f0938fbcae11a66cebf3e7ac92d2104e8f5 /Porting/todo.pod
parent03548f30e402504a7edba200e0bcb3605798d0c8 (diff)
downloadperl-2a930eeaa11a10dc2ffcb200563ba5641ac15840.tar.gz
Remove the reference to -fstack-protector, which is done.
Exploring the use of -D_FORTIFY_SOURCE=2 remains to be done.
Diffstat (limited to 'Porting/todo.pod')
-rw-r--r--Porting/todo.pod9
1 files changed, 4 insertions, 5 deletions
diff --git a/Porting/todo.pod b/Porting/todo.pod
index 75bc3f1c02..8e38e8fe41 100644
--- a/Porting/todo.pod
+++ b/Porting/todo.pod
@@ -500,14 +500,13 @@ ever creep back to libperl.a.
Note, of course, that this will only tell whether B<your> platform
is using those naughty interfaces.
-=head2 -D_FORTIFY_SOURCE=2, -fstack-protector
+=head2 -D_FORTIFY_SOURCE=2
-Recent glibcs support C<-D_FORTIFY_SOURCE=2> and recent gcc
-(4.1 onwards?) supports C<-fstack-protector>, both of which give
+Recent glibcs support C<-D_FORTIFY_SOURCE=2> which gives
protection against various kinds of buffer overflow problems.
-These should probably be used for compiling Perl whenever available,
+It should probably be used for compiling Perl whenever available,
Configure and/or hints files should be adjusted to probe for the
-availability of these features and enable them as appropriate.
+availability of these feature and enable it as appropriate.
=head2 Arenas for GPs? For MAGIC?