public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54833] Don't wrap __builtin_free(a) in if (a != NULL)
Date: Sun, 07 Oct 2012 15:52:00 -0000 [thread overview]
Message-ID: <bug-54833-4-Soa4iJ1gCC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54833-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54833
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-07 15:51:51 UTC ---
It depends on what is the probability that the pointer is NULL. If it is
unlikely, then unconditional free is the right choice, if NULL is very likely,
then the test may be less expensive (avoids call including likely PLT slot
overhead and comparison at least).
next prev parent reply other threads:[~2012-10-07 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 10:13 [Bug fortran/54833] New: " tkoenig at gcc dot gnu.org
2012-10-06 10:13 ` [Bug fortran/54833] " tkoenig at gcc dot gnu.org
2012-10-07 15:52 ` jakub at gcc dot gnu.org [this message]
2015-08-31 10:55 ` fxcoudert at gcc dot gnu.org
2015-08-31 10:55 ` fxcoudert 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-54833-4-Soa4iJ1gCC@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).