[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-12-03 Thread James Keenan via RT
No complaints heard; resolving ticket.

[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-12-02 Thread James Keenan via RT
Patch was committed to trunk 01 Dec in r23331.

[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-11 Thread James Keenan via RT
The patch attached changes x86 - stack and ppc - register in the relevant files. I have tested it successfully in a 'stack' environment (Linux x86) but don't have a 'register' environment in which to test it. Can someone please help out here? I would then apply it to trunk. kid51 Index:

[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread James Keenan via RT
On Fri Nov 09 23:31:56 2007, [EMAIL PROTECTED] wrote: It in no way refers to architecture actually. It refers to the calling convention on an architecture(dependent upon implementation). The x86 method is by pushing arguments onto the stack, and the ppc method is in registers. On amd64,

Re: [perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread Joshua Isom
On Nov 10, 2007, at 7:42 AM, James Keenan via RT wrote: On Fri Nov 09 23:31:56 2007, [EMAIL PROTECTED] wrote: It in no way refers to architecture actually. It refers to the calling convention on an architecture(dependent upon implementation). The x86 method is by pushing arguments onto

Re: [perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread chromatic
On Friday 09 November 2007 23:28:52 Joshua Isom wrote: It in no way refers to architecture actually. It refers to the calling convention on an architecture(dependent upon implementation). The x86 method is by pushing arguments onto the stack, and the ppc method is in registers. On amd64,

[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread James Keenan via RT
On Sat Nov 10 11:55:07 2007, [EMAIL PROTECTED] wrote: How about stack and register, or are there better labels? If it's confusing now, it will probably be confusing in the future, especially for everyone who doesn't know it's the platform ABI. So if we were to change: x86 - stack

Re: [perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread chromatic
On Saturday 10 November 2007 15:48:08 James Keenan via RT wrote: On Sat Nov 10 11:55:07 2007, [EMAIL PROTECTED] wrote: How about stack and register, or are there better labels? If it's confusing now, it will probably be confusing in the future, especially for everyone who doesn't know

Re: [perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-10 Thread ajr
How about stack and register, or are there better labels? If it's confusing now, it will probably be confusing in the future, especially for everyone who doesn't know it's the platform ABI. That sounds like the essential distinction to me. While I was researching the topic, I came across

[perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-09 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #47313] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47313 The description for Parrot configuration step class auto::va_ptr states that its

Re: [perl #47313] [BUG] config/auto/va_ptr.pm delivering surprising result

2007-11-09 Thread Joshua Isom
On Nov 9, 2007, at 8:08 PM, James Keenan (via RT) wrote: # New Ticket Created by James Keenan # Please include the string: [perl #47313] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47313 The description for