public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>,
	    Nathan Sidwell <nathan@acm.org>
Subject: Re: [PATCH] Add malloc predictor (PR middle-end/83023).
Date: Fri, 27 Jul 2018 12:38:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1807271428130.25712@stedding.saclay.inria.fr> (raw)
In-Reply-To: <e1408fe5-eba6-f616-bc9a-1f4416cdc401@suse.cz>

On Fri, 27 Jul 2018, Martin Liška wrote:

> So answer is yes, the builtin can be then removed.

Good, thanks. While looking at how widely it is going to apply, I noticed 
that the default, throwing operator new has attribute malloc and 
everything, but the non-throwing variant declared in <new> doesn't, so it 
won't benefit from the new predictor. I don't know if there is a good 
reason for this disparity...

-- 
Marc Glisse

  reply	other threads:[~2018-07-27 12:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 14:43 Martin Liška
2018-07-26 15:00 ` Marc Glisse
2018-07-27 12:05   ` Martin Liška
2018-07-27 12:38     ` Marc Glisse [this message]
2018-08-01 11:04       ` Martin Liška
2018-08-01 11:28       ` Martin Liška
2018-08-01 12:25         ` Marc Glisse
2018-08-01 12:44           ` Martin Liška
2018-08-01 15:05             ` Marc Glisse
2018-08-02 10:59               ` Martin Liška
2018-08-07 11:51                 ` Jan Hubicka
2018-08-07 11:59                   ` Martin Liška
2018-08-01 15:11           ` Nathan Sidwell
2018-07-31  9:25 ` Jan Hubicka
2018-08-01 11:30   ` Martin Liška

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=alpine.DEB.2.21.1807271428130.25712@stedding.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mliska@suse.cz \
    --cc=nathan@acm.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).