public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94722] implement __attribute__((no_stack_protector)) function attribute
Date: Thu, 22 Oct 2020 08:11:43 +0000 [thread overview]
Message-ID: <bug-94722-4-tbwKmqBPdM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94722-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94722
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:346b302d09c1e6db56d9fe69048acb32fbb97845
commit r11-4218-g346b302d09c1e6db56d9fe69048acb32fbb97845
Author: Martin Liska <mliska@suse.cz>
Date: Fri May 15 14:42:12 2020 +0200
Implement no_stack_protector attribute.
gcc/ChangeLog:
2020-05-18 Martin Liska <mliska@suse.cz>
PR c/94722
* cfgexpand.c (stack_protect_decl_phase):
Guard with lookup_attribute("no_stack_protector") at
various places.
(expand_used_vars): Likewise here.
* doc/extend.texi: Document no_stack_protector attribute.
gcc/ada/ChangeLog:
2020-05-18 Martin Liska <mliska@suse.cz>
PR c/94722
* gcc-interface/utils.c (handle_no_stack_protect_attribute):
New.
(handle_stack_protect_attribute): Add error message for a
no_stack_protector function.
gcc/c-family/ChangeLog:
2020-05-18 Martin Liska <mliska@suse.cz>
PR c/94722
* c-attribs.c (handle_no_stack_protect_function_attribute): New.
(handle_stack_protect_attribute): Add error message for a
no_stack_protector function.
gcc/testsuite/ChangeLog:
2020-05-18 Martin Liska <mliska@suse.cz>
PR c/94722
* g++.dg/no-stack-protector-attr-2.C: New test.
* g++.dg/no-stack-protector-attr-3.C: New test.
* g++.dg/no-stack-protector-attr.C: New test.
next prev parent reply other threads:[~2020-10-22 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 21:03 [Bug c/94722] New: " ndesaulniers at google dot com
2020-04-22 21:16 ` [Bug c/94722] " joseph at codesourcery dot com
2020-04-22 21:28 ` ndesaulniers at google dot com
2020-04-22 21:30 ` ndesaulniers at google dot com
2020-04-23 5:31 ` marxin at gcc dot gnu.org
2020-10-22 8:11 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-22 8:13 ` marxin at gcc dot gnu.org
2020-12-17 5:34 ` i at maskray dot me
2020-12-17 8:37 ` marxin at gcc dot gnu.org
2020-12-17 8:52 ` jakub at gcc dot gnu.org
2020-12-18 0:17 ` ndesaulniers at google dot com
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-94722-4-tbwKmqBPdM@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).