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-patches@gcc.gnu.org>
Subject: Re: [patch i386]: Add for win32 targets pre-prologue profiling 	feature
Date: Sun, 18 Jul 2010 12:20:00 -0000	[thread overview]
Message-ID: <AANLkTikAwuiC8h-3JkvhTb1qCCRMUh9sHVqv8AEcn_1c@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007162251310.5661@acrux.dbai.tuwien.ac.at>

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

2010/7/16 Gerald Pfeifer <gerald@pfeifer.com>:
> On Thu, 15 Jul 2010, Kai Tietz wrote:
>>       * doc/invoke.texi (mfentry): Add documentation.
>
> +Note: On x86 architectures the attribute @code{ms_hook_prologue}
> +isn't possible at the moment for @option{-mfentry} and @option{-pg}.
>
> How about: "...is not supported for...at the moment."?
>
> And if you could add an item to http://gcc.gnu.org/gcc-4.6/changes.html
> when this goes in, that would be good.
>
> Gerald
>

Something like this?

Regards,
Kai

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

[-- Attachment #2: gcc46_change_profile.diff --]
[-- Type: application/octet-stream, Size: 438 bytes --]

Index: gcc-4.6/changes.html
===================================================================
--- gcc-4.6.orig/changes.html	2010-07-16 13:35:00.000000000 +0200
+++ gcc-4.6/changes.html	2010-07-18 14:18:14.061973200 +0200
@@ -197,7 +197,8 @@
 
 <h3>IA-32/x86-64</h3>
   <ul>
-    <li>...</li>
+	<li>Support of emitting profiler counter call before prologue via
+	command line option <code>-mfentry</code>.</li>
   </ul>
 
 <h3>MIPS</h3>

  reply	other threads:[~2010-07-18 12:20 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 [this message]
2010-07-18 20:52               ` Gerald Pfeifer
2010-07-18 20:54                 ` Kai Tietz
2010-07-28 18:06                 ` Kai Tietz
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=AANLkTikAwuiC8h-3JkvhTb1qCCRMUh9sHVqv8AEcn_1c@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).