[omniORB] Incorrect processor define on Apple M1

[Duncan Grisby]

On Fri, 2023-04-14 at 12:36 +0200, Thomas Braun via omniORB-list wrote:


> we do have some issues on cppTango, which uses omniORB, with obvious
> crashes on Apple M1.
> 
> The problem seems to be that the omniORB pkg-config files use the
> wrong processor defines.

[...]
> and that gives
> 
> PROCESSOR_DEFINE='__arm__'
> PROCESSOR_NAME='ArmProcessor'

I agree that it is not quite right. However, I am not sure how that
could lead to a crash. The only place in omniORB that actually looks at
that processor define is where it handles the old ARM mixed-endian
double format. It certainly could become confused and break double
precision values, which would clearly be bad, but it would not crash.

Or is it that the definition of __arm__ somehow breaks some other code
that is not in omniORB?

If the crash is in omniORB, can you give a stack trace for it?

Duncan.


-- 
 -- Duncan Grisby --
  -- duncan at grisby.org --
   -- http://www.grisby.org --