From: Jakub Jelinek <jakub@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: drepper@redhat.com, libc-hacker@sources.redhat.com
Subject: Re: [PATCH]: Sparc SUN4V Niagara optimized memset/memcpy
Date: Wed, 01 Mar 2006 22:31:00 -0000 [thread overview]
Message-ID: <20060301223039.GL30252@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <20060301.142533.76669771.davem@davemloft.net>
On Wed, Mar 01, 2006 at 02:25:33PM -0800, David S. Miller wrote:
> From: Ulrich Drepper <drepper@redhat.com>
> Date: Wed, 01 Mar 2006 13:31:51 -0800
>
> > The ENTRY macro should get cfi_ support. Then you cannot nest
> > .cfi_startproc. cfi is not optional.
>
> ok.
Sure, but you can use naked .globl __bzero; .type __bzero, @function; __bzero:
in this case or create a special macro for alternate entry point.
Jakub
next prev parent reply other threads:[~2006-03-01 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 8:55 David S. Miller
2006-03-01 15:49 ` Ulrich Drepper
2006-03-01 21:19 ` David S. Miller
2006-03-01 21:30 ` Ulrich Drepper
2006-03-01 22:25 ` David S. Miller
2006-03-01 22:31 ` Jakub Jelinek [this message]
2006-03-01 22:48 ` David S. Miller
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=20060301223039.GL30252@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=davem@davemloft.net \
--cc=drepper@redhat.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).