Re: [Gcl-devel] Re: (object (*)()) vs (long (*)())

2002-08-02 Thread Camm Maguire
Greetings! OK, you convinced me! I'm uploading now... Take care, Andreas Schwab <[EMAIL PROTECTED]> writes: > Camm Maguire <[EMAIL PROTECTED]> writes: > > |> Greetings, and thanks for your *very helpful* reply! > |> > |> OK, now it is clear to me what is going on. I calling all functions >

Re: [Gcl-devel] Re: (object (*)()) vs (long (*)())

2002-08-02 Thread Andreas Schwab
Camm Maguire <[EMAIL PROTECTED]> writes: |> Greetings, and thanks for your *very helpful* reply! |> |> OK, now it is clear to me what is going on. I calling all functions |> through a variable declared to return a pointer, and some functions |> are returning a long. |> |> I can fix the instance

Re: [Gcl-devel] Re: (object (*)()) vs (long (*)())

2002-08-01 Thread Camm Maguire
Greetings, and thanks for your *very helpful* reply! OK, now it is clear to me what is going on. I calling all functions through a variable declared to return a pointer, and some functions are returning a long. I can fix the instances in the existing code fairly easily, but the issue is that the

Re: (object (*)()) vs (long (*)())

2002-08-01 Thread Andreas Schwab
Peter Barada <[EMAIL PROTECTED]> writes: |> >Function return values must be declared (and used) properly on m68k, |> >pointer values are returned in reg a0, ints d0. I would be surprised |> >if m68k was the only arch that gets broken by this.. |> |> Which OS support his ABI? I'd like to know so

Re: (object (*)()) vs (long (*)())

2002-07-31 Thread Richard Zidlicky
On Wed, Jul 31, 2002 at 02:51:25PM +0200, Andreas Schwab wrote: > |> Function return values must be declared (and used) properly on m68k, > |> pointer values are returned in reg a0, ints d0. I would be surprised > |> if m68k was the only arch that gets broken by this.. > > Actually, this should

Re: (object (*)()) vs (long (*)())

2002-07-31 Thread Peter Barada
>Function return values must be declared (and used) properly on m68k, >pointer values are returned in reg a0, ints d0. I would be surprised >if m68k was the only arch that gets broken by this.. Which OS support his ABI? I'd like to know so I can be sure that my ColdFire v4/v4e changes produce co

Re: (object (*)()) vs (long (*)())

2002-07-31 Thread Andreas Schwab
Richard Zidlicky <[EMAIL PROTECTED]> writes: |> cc'd linux-m68k as this seems more appropriate for ABI related |> questions. |> |> On Tue, Jul 30, 2002 at 01:42:17PM -0400, Camm Maguire wrote: |> > Greetings! I'm maintaining gcl, which, fortunately or not, relies on |> > being able to cast funct

Re: (object (*)()) vs (long (*)())

2002-07-31 Thread Richard Zidlicky
cc'd linux-m68k as this seems more appropriate for ABI related questions. On Tue, Jul 30, 2002 at 01:42:17PM -0400, Camm Maguire wrote: > Greetings! I'm maintaining gcl, which, fortunately or not, relies on > being able to cast function results back and forth from long to void > *. this should

(object (*)()) vs (long (*)())

2002-07-30 Thread Camm Maguire
Greetings! I'm maintaining gcl, which, fortunately or not, relies on being able to cast function results back and forth from long to void *. (The 'object' above is a pointer to a union). This works everywhere except on m68k, where I can stop at a certain point in a debugger, and get different re