Re: [PATCH 2/8] UML - Define jmpbuf access constants

On 2/6/06, Jeff Dike <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 2/8] UML - Define jmpbuf access constants
    • From: Jeff Dike <[email protected]>

• References:
  • [PATCH 2/8] UML - Define jmpbuf access constants
    • From: Jeff Dike <[email protected]>

• Prev by Date: Re: [PATCH] percpu data: only iterate over possible CPUs
• Next by Date: kernel + klibc tree now, in theory, feature-complete
• Previous by thread: [PATCH 2/8] UML - Define jmpbuf access constants
• Next by thread: Re: [PATCH 2/8] UML - Define jmpbuf access constants
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]