public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: davidm@hpl.hp.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] move __gmon_start__ call out of .init section
Date: Thu, 07 Nov 2002 17:43:00 -0000	[thread overview]
Message-ID: <200211080143.gA81hXp29892@magilla.sf.frob.com> (raw)
In-Reply-To: David Mosberger's message of  Thursday, 7 November 2002 14:32:48 -0800 <15818.59920.66031.178917@napali.hpl.hp.com>

> We wouldn't be putting __gmon_init__ directly into .preinit---we would
> put a function there which will then check whether __gmon_init__ is
> NULL and, if not, call it.

Oh, well I don't see any potential problem with that then.  

> Hmmh, I'm sorry about that.  I was using a script that Uli sent me
> some time ago.  I'm not a (heavy) CVS user but Uli told me that the
> patches created by "cvs diff -U" are broken.  What's the recommend way
> to create a diff from the glibc CVS?

My cvs version calls itself 1.11.1p1, and it produces diffs with proper
file names in them for cvs diff by itself.  Probably yours does too, and
the script you are using that was necessary for older cvs versions does not
mix well with already-correct input.

  reply	other threads:[~2002-11-08  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  7:00 David Mosberger
2002-11-07 13:45 ` Roland McGrath
2002-11-07 14:08   ` David Mosberger
2002-11-07 14:27     ` Roland McGrath
2002-11-07 14:32       ` David Mosberger
2002-11-07 17:43         ` Roland McGrath [this message]
2002-11-08  3:05           ` Andreas Schwab
2002-11-08 11:15           ` David Mosberger

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=200211080143.gA81hXp29892@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=libc-hacker@sources.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).