I have just noticed that CFLAGS suggested by Config also include -D_FORTIFY_SOURCE=2 which causes the compiler to warn me that because of this it needs -O! So the question now is whether I need to use -D_FORTIFY_SOURCE=2 in compiling my perl-embed C programs or I can safely ignore it, at least when I need to debug.

-D_REENTRANT -D_GNU_SOURCE -O2 -g -pipe -Wall -Werror=format-security 
+-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param
+=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/r
+edhat-hardened-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -
+fwrapv -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE 
+-D_FILE_OFFSET_BITS=64

[download]

In reply to Re: Config sets optimisation compilation flags (-O/-g)! by bliako
in thread Config sets optimisation compilation flags (-O/-g)! by bliako

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.