Re: aix tinderbox failure

2004-03-28 Thread Adam Thomason
Actually, it'd be better just to remove jit_debug_xcoff.c from the build for now, 
since it never really worked (the bugs it was designed to help with were independently 
resolved).  AFAICT the object code it produces is correct, but I was unable to make 
gdb (and certainly not dbx) import the XCOFF stabs symbols, so its value is marginal 
at best.  Attached patch removes it and associated build hooks, as well as fixing some 
compiler warnings.  If there's a need for it in the future it can be restored from the 
CVS attic.

Adam

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 28, 2004 6:05 AM
> To: Perl6 Internals
> Subject: aix tinderbox failure
> 
> 
> Hi,
> 
> currently the aix tinderbox is failing. It chokes on
> bufstart/buflen which were hacky accessors to PMC data and 
> were removed recently. I think changing jit_debug_xcoff.c 
> would remove at last this error. Can someone on AIX check this ?
> 
> bö
> 
> 


xcoff_stabs.patch
Description: xcoff_stabs.patch


Re: aix tinderbox failure

2004-03-28 Thread Leopold Toetsch
Juergen Boemmels <[EMAIL PROTECTED]> wrote:

> currently the aix tinderbox is failing. It chokes on bufstart/buflen

Thanks, applied.
leo


aix tinderbox failure

2004-03-28 Thread Juergen Boemmels
Hi,

currently the aix tinderbox is failing. It chokes on bufstart/buflen
which were hacky accessors to PMC data and were removed recently. I
think changing jit_debug_xcoff.c would remove at last this error. Can
someone on AIX check this ?

bö

Index: src/jit_debug_xcoff.c
===
RCS file: /cvs/public/parrot/src/jit_debug_xcoff.c,v
retrieving revision 1.3
diff -u -r1.3 jit_debug_xcoff.c
--- src/jit_debug_xcoff.c	26 Jan 2004 23:16:05 -	1.3
+++ src/jit_debug_xcoff.c	28 Mar 2004 13:41:10 -
@@ -122,8 +122,8 @@
 "strstart:15,%d,%d;"/* fake a char* */
 ";\""
 ",0," C_DECL ",0\n", i++, BYTE_SIZE(STRING),
-BIT_OFFSET(STRING, bufstart), BIT_SIZE(void*),
-BIT_OFFSET(STRING, buflen), BIT_SIZE(size_t),
+BIT_OFFSET(STRING, obj.u._b._bufstart), BIT_SIZE(void*),
+BIT_OFFSET(STRING, obj.u._b._buflen), BIT_SIZE(size_t),
 BIT_OFFSET(STRING, obj.flags), BIT_SIZE(UINTVAL),
 BIT_OFFSET(STRING, bufused), BIT_SIZE(UINTVAL),
 BIT_OFFSET(STRING, strstart), BIT_SIZE(void*)


Re: Windows tinder builds

2004-03-28 Thread Steve Fink
On Mar-26, Dan Sugalski wrote:
> The VS/.NET build works fine, though three of the tests fail for odd 
> reasons. Those look like potential test harness errors.
> 
> The cygwin build sorta kinda works OK, but the link fails because of 
> a missing _inet_pton. I seem to remember this cropping up in the past 
> and I thought we'd gotten it fixed, but apparently not.
> 
> Anyway, these are set for hourly builds at half-hour offsets, so if 
> you check in any significant changes it'd be advisable to take a look 
> at the results. For those that don't know, all the tinderbox info is 
> web-accessable at 
> http://tinderbox.perl.org/tinderbox/bdshowbuild.cgi?tree=parrot

A couple of weeks back, I also beefed up the error parsing stuff a bit
on my Parrot tinderbox summarizer at
http://foxglove.dnsalias.org/parrot/ so that it should give a good
"what's broken and why" summary at a glance.

Note that because I only run the summarizer once an hour at 17 minutes
past the hour, it is not the right place to go if you're watching to
see if your commit broke anything. For that, see the official URL
above.