Re: [RFC] Endianness and signals

From: David Mosberger <>
Date: 2003-10-22 06:56:49
>>>>> On Tue, 21 Oct 2003 13:37:00 -0700, Cary Coutant <> said:

  Cary> I think the right thing to do is set the bit on
  Cary> delivery of a signal to match (elf_header.e_flags &
  Cary> EF_IA_64_BE).

The kernel does not support the loading of big-endian executables, so
this would be equivalent to always clearing on a signal.

  Cary> I'm not sure I buy the argument that you shouldn't change the
  Cary> behavior now because it's been that way for a long time. What
  Cary> you have now is unpredictable, so the only ways a signal
  Cary> handler could work in an application that switches the
  Cary> bit on a regular basis are: (1) it just gets lucky, and never
  Cary> gets an interrupt while in the wrong state, (2) the
  Cary> application blocks signals while in the opposite state, or (3)
  Cary> the signal handler forces the to what it wants. In any
  Cary> of these cases, the proposed behavior will work.

The fourth case is that the application has signal handlers that
expect to get called in the "opposite" byte-order and those are the
ones that would break if we changed the current behavior.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Tue Oct 21 17:01:00 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:19 EST