public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: [PING 5] Re: [PATCH]  warn for unsafe calls to __builtin_return_addres
Date: Tue, 21 Jul 2015 01:58:00 -0000	[thread overview]
Message-ID: <55AD8967.3040706@gmail.com> (raw)
In-Reply-To: <55A4830B.1030008@gmail.com>

Ping #5.

On 07/13/2015 09:33 PM, Martin Sebor wrote:
> Still looking for a review of this small patch to help detect
> potentially unsafe calls to __builtin_{frame,return}_address
> (with an argument > 2) that tend to either return bogus values
> or lead to crashes at runtime.
>
> The problem the function can cause was originally reported in
> pr8743 and resolved by adding a note to the documentation. This
> patch tweaks the documentation further to make the risks of
> using the function that much clearer.
>
>    https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00886.html
>
> Thanks
> Martin

      reply	other threads:[~2015-07-20 23:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  3:33 [PING 4] " Martin Sebor
2015-07-21  1:58 ` Martin Sebor [this message]

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=55AD8967.3040706@gmail.com \
    --to=msebor@gmail.com \
    --cc=gcc-patches@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).