public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Richard Henderson <rth@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	gcc-patches@gcc.gnu.org
Subject: Re: [patch i386]: Add for win32 targets pre-prologue profiling 	feature
Date: Wed, 28 Jul 2010 18:06:00 -0000	[thread overview]
Message-ID: <AANLkTikTcgTNVV2vZnYUQ0mt=SeDYOPXsWGCVW-_QOLq@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007182250190.5661@acrux.dbai.tuwien.ac.at>

2010/7/18 Gerald Pfeifer <gerald@pfeifer.com>:
> On Sun, 18 Jul 2010, Kai Tietz wrote:
>> Something like this?
>
> +       <li>Support of emitting profiler counter call before prologue via
> +       command line option <code>-mfentry</code>.</li>
>
> How about
>
>  <li>Support for emitting profiler counter calls before function
>  prologues.  This is enabled via a new command-line option
>  <code>-mfentry</code>.</li>
>
> ?
>
> If this, or a variation, is fine with you, let's give Richard a day or
> two to comment and then go ahead and commit.
>
> Thanks,
> Gerald
>

Ok, added changelog entry as

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v
retrieving revision 1.33
diff -u -3 -r1.33 changes.html
--- changes.html        24 Jul 2010 19:37:48 -0000      1.33
+++ changes.html        28 Jul 2010 18:02:55 -0000
@@ -200,7 +200,9 @@

 <h3>IA-32/x86-64</h3>
   <ul>
-    <li>...</li>
+       <li>Support for emitting profiler counter calls before function
+       prologues.  This is enabled via a new command-line option
+       <code>-mfentry</code>.</li>
   </ul>

 <h3>MIPS</h3>

Regards,
Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

  parent reply	other threads:[~2010-07-28 18:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 12:47 Kai Tietz
2010-07-13 16:28 ` Richard Henderson
2010-07-14 10:20   ` Kai Tietz
2010-07-14 11:49     ` Dave Korn
2010-07-14 12:11       ` Kai Tietz
2010-07-14 12:16     ` Andi Kleen
2010-07-14 12:38       ` Kai Tietz
2010-07-15 18:08         ` Kai Tietz
2010-07-16 17:06           ` Richard Henderson
2010-07-17  6:52             ` Kai Tietz
2010-07-20  2:27               ` Richard Henderson
2010-07-28  8:36                 ` Kai Tietz
2010-07-28 16:00                   ` Richard Henderson
2010-07-28 16:01                     ` Andi Kleen
2010-07-28 17:28                       ` Kai Tietz
2010-07-28 17:40                         ` Richard Henderson
2010-07-28 18:14                           ` Kai Tietz
2010-07-16 20:53           ` Gerald Pfeifer
2010-07-18 12:20             ` Kai Tietz
2010-07-18 20:52               ` Gerald Pfeifer
2010-07-18 20:54                 ` Kai Tietz
2010-07-28 18:06                 ` Kai Tietz [this message]
2010-07-16 23:57           ` Andi Kleen
2010-07-17  5:34             ` Kai Tietz
2010-07-17  9:45               ` Andi Kleen
2010-07-18 11:37                 ` Kai Tietz
2010-07-18 11:46                   ` Kai Tietz

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='AANLkTikTcgTNVV2vZnYUQ0mt=SeDYOPXsWGCVW-_QOLq@mail.gmail.com' \
    --to=ktietz70@googlemail.com \
    --cc=andi@firstfloor.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=rth@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).