From: Ulrich Drepper <drepper@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [PATCH 2/8] UML - Define jmpbuf access constants
Date: Tue, 7 Feb 2006 09:37:13 -0800 [thread overview]
Message-ID: <a36005b50602070937h60e35294q1dbef2c21f2fb50d@mail.gmail.com> (raw)
In-Reply-To: <200602070223.k172NpJa009654@ccure.user-mode-linux.org>
On 2/6/06, Jeff Dike <jdike@addtoit.com> wrote:
> With newer libcs, the JB_* macros (which we shouldn't be using anyway,
> probably) go away.
I assume you have your own setjmp implementation and are not using the
libc version?
If you don't then there is a problem. There is a good reason why the
constants are removed: you couldn't use the values anyway. Your don't
have the information to "decrypt" them. If you just used the values
and implemented the function yourself, fine.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-02-07 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 2:23 [uml-devel] [PATCH 2/8] UML - Define jmpbuf access constants Jeff Dike
2006-02-07 17:37 ` Ulrich Drepper [this message]
2006-02-07 18:57 ` [uml-devel] " Jeff Dike
2006-02-07 19:23 ` Ulrich Drepper
2006-02-08 16:43 ` Jeff Dike
2006-06-04 18:19 ` [uml-devel] " Blaisorblade
2006-06-05 15:40 ` Jeff Dike
2006-06-07 17:33 ` Blaisorblade
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=a36005b50602070937h60e35294q1dbef2c21f2fb50d@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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