public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dnovillo at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/20318] RFE: add attribute to specify that a function never returns NULL Date: Fri, 04 Mar 2005 17:59:00 -0000 [thread overview] Message-ID: <20050304175951.19445.qmail@sourceware.org> (raw) In-Reply-To: <20050304153241.20318.jorton@redhat.com> ------- Additional Comments From dnovillo at redhat dot com 2005-03-04 17:59 ------- Subject: Re: RFE: add attribute to specify that a function never returns NULL giovannibajo at libero dot it wrote: > ------- Additional Comments From giovannibajo at libero dot it 2005-03-04 17:53 ------- > I don't object that this feature is indeed needed, but I would still like to > see a reduced testcase from Subversion which shows a bogus warning that could > be fixed with this attribute. > I have attached the pre-processed test case from Joe. > BTW, Diego, once ASSERT_EXPR becomes a generic node, can't just the C++ FE uses > it to assert that the return value for a CALL_EXPR to an allocation function is > non-zero? > The attribute would be enough. The FE need only set an ECF_ flag to the CALL_EXPR and the optimizers will pick it up from there. Diego. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20318
next prev parent reply other threads:[~2005-03-04 17:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-04 15:32 [Bug c/20318] New: " jorton at redhat dot com 2005-03-04 15:38 ` [Bug c/20318] " pinskia at gcc dot gnu dot org 2005-03-04 17:53 ` giovannibajo at libero dot it 2005-03-04 17:59 ` dnovillo at redhat dot com [this message] 2005-03-04 18:01 ` dnovillo at gcc dot gnu dot org 2005-06-03 14:20 ` pinskia at gcc dot gnu dot org [not found] <bug-20318-10211@http.gcc.gnu.org/bugzilla/> 2005-11-11 23:29 ` green at redhat dot com 2005-11-12 19:26 ` pinskia at gcc dot gnu dot org 2006-01-09 18:34 ` pinskia at gcc dot gnu dot org [not found] <bug-20318-4@http.gcc.gnu.org/bugzilla/> 2013-10-09 13:03 ` glisse at gcc dot gnu.org 2013-10-11 11:48 ` glisse 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=20050304175951.19445.qmail@sourceware.org \ --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: linkBe 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).