public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions
Date: Tue, 27 Aug 2013 02:08:00 -0000	[thread overview]
Message-ID: <bug-58245-4-aXTurKm5Q8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58245-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245

--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> ---
One more thing: I would be happy with either of two solutions, either:

(1) Checking the canary before calling a noreturn function, just like
performing a check before a tail-call, or

(2) Eliminating the dead-code-removal of the function epilogue at -O0, and for
non-zero -O levels, adding an optimization to remove the canary loading from
the prologue if no epilogue to check the canary is to be generated.


  reply	other threads:[~2013-08-27  2:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  2:06 [Bug middle-end/58245] New: " bugdal at aerifal dot cx
2013-08-27  2:08 ` bugdal at aerifal dot cx [this message]
2013-08-27  2:23 ` [Bug middle-end/58245] " pinskia at gcc dot gnu.org
2013-08-27  2:35 ` bugdal at aerifal dot cx
2013-08-28 13:10 ` rose.garcia-eggl2fk at yopmail dot com
2013-10-01 14:07 ` timo.teras at iki dot fi
2013-10-01 15:44 ` jakub at gcc dot gnu.org
2013-10-01 17:18 ` bugdal at aerifal dot cx
2014-01-15 14:24 ` basile at opensource dot dyc.edu
2014-02-16 13:16 ` jackie.rosen at hushmail dot com
2022-07-13 22:49 ` pinskia at gcc dot gnu.org
2022-07-13 23:19 ` hjl.tools at gmail dot com
2022-07-13 23:19 ` hjl.tools at gmail dot com
2022-09-28  1:30 ` 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-58245-4-aXTurKm5Q8@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).