public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH][C++] Annotate more functions with MEM-STATs
Date: Fri, 17 Feb 2017 12:59:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1702171329220.8538@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20170217122750.GI1849@tucnak>

On Fri, 17 Feb 2017, Jakub Jelinek wrote:

> On Fri, Feb 17, 2017 at 01:22:57PM +0100, Richard Biener wrote:
> > And even unify CXX_MEM_STAT_INFO and MEM_STAT_INFO, also dropping support
> > for host compilers < GCC 4.8, GCC 4.8 introduced __builtin_FILE and
> > friends (you'd have to bootstrap with older host compilers or clang
> > which doesn't seem to support those either and still claims to be
> > GCC 4.2.1 ...).
> 
> Do you mean drop support for host < GCC 4.8 if detailed mem stats gathering
> is requested, or dropping support for such host compilers altogether?
> I have no problem with the former, big problem with the latter.

The former, and it would just make stage1 more-or-less behave as if
detailed mem stats gathering would be disabled (with a simple-minded
approach GATHER_STATISTICS would still be 1 but all MEM_STAT_DECL, etc.
would expand to nothing, thus require __builtin_FILE () support).

Richard.

  reply	other threads:[~2017-02-17 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 12:23 Richard Biener
2017-02-17 12:27 ` Richard Biener
2017-02-17 12:30   ` Jakub Jelinek
2017-02-17 12:59     ` Richard Biener [this message]
2017-02-18  4:53 ` Jason Merrill
2017-04-21  9:27   ` Richard Biener

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.LSU.2.20.1702171329220.8538@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    /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).