Dear All,
Could we add a 'Hello World.pasm' to 'parrot/examples/assembly'?
Joe Yates
Dan Sugalski wrote:
Okay, this has been sitting around for a while, and it's time to dump
it. This is reasonably high-level, and a bit terse, so I'm throwing it
out for discussion/addition/fleshing out. Comments, please. (As if I
have to ask... :)
Do you have a less terse version?
*) IMCC
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) Fixed disassembler
I will volunteer to take over on this and get it working if no one has
time for it.
> *) Working "make install"
see next note :
*) Support for cross compilation
i think that it is important that we really come to terms with the
On Mon, Jan 13, 2003 at 06:12:59AM -0800, James Michael DuPont wrote:
> *) Support for cross compilation
> i think that it is important that we really come to terms with the new
> configure tool. To be honest, i like the idea of using a perl based
> configurator, and my research into autoconf and
--- Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 13, 2003 at 06:12:59AM -0800, James Michael DuPont wrote:
>
> > *) Support for cross compilation
> > i think that it is important that we really come to terms with the
> new
> > configure tool. To be honest, i like the idea of using a p
On Fri, 10 Jan 2003 11:49:14 -0500, Dan Sugalski wrote:
> At 1:37 PM + 1/10/03, Peter Haworth wrote:
> >On Thu, 9 Jan 2003 16:40:20 -0500, Dan Sugalski wrote:
> >> #10 We do MI, but we don't instantiate a class' attributes multiple
> >>times if its in the hierarchy for a class more than on
At 10:12 PM -0800 1/12/03, Mr. Nobody wrote:
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
*) ICU building
*) Unicode encoding
Do we really need unicode in parrot?
Yes, we do. There's a lot of data out in the world that's Unicode-encoded.
Seems to me like it dosen't really
accomplish much
At 10:08 AM +0100 1/13/03, Leopold Toetsch wrote:
Dan Sugalski wrote:
Okay, this has been sitting around for a while, and it's time to
dump it. This is reasonably high-level, and a bit terse, so I'm
throwing it out for discussion/addition/fleshing out. Comments,
please. (As if I have to ask..
On Fri, Jan 10, 2003 at 01:05:05PM +0100, Leopold Toetsch wrote:
> >While I'd like no stack walking, as it's pricey, I'm not sure it's
> >tenable.
>
> As the current clone changes does show, it's possible.
>
> BTW current tests do succed w/o stackwalking - its disabled.
>
> >... Skipping it m
At 6:12 AM -0800 1/13/03, James Michael DuPont wrote:
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
*) Fixed disassembler
I will volunteer to take over on this and get it working if no one has
time for it.
I had a fix for it in my inbox, so I applied it and this is no longer
an issue. :)
> *
Nicholas Clark wrote:
IIRC Leo added an option to Configure.pl to turn on optimising.
Yep.
Has anyone [er, I'm thinking of Leo :-)] tried benchmarking computed goto
without this flag? And with the various align functions, such as
-falign-jumps ?
-O3 -fno-gcse doesn't compile the core_ops
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 6:12 AM -0800 1/13/03, James Michael DuPont wrote:
> >--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> >> *) Fixed disassembler
> >I will volunteer to take over on this and get it working if no one
> has
> >time for it.
>
> I had a fix for it in my i
On Mon, Jan 13, 2003 at 05:14:54PM +0100, Leopold Toetsch wrote:
> The -malign flags seem to have reasonable defaults.
As in you've read what they are, and they seem reasonable, or you've
actually tested the timings when playing with them?
colon has too much load ("damn users" (of which I'm one))
Too simple.. There is some good documentation though and the examples,
while a bit too complex at first can be understood after ahile. I hate
having to relearn assembly though, it's been too long.
helloworld.pasm:
print "Hello World!\n"
Joe Yates wrote:
Dear All,
Could we add a 'Hello World
At 10:35 AM -0600 1/13/03, Joseph Guhlin wrote:
Too simple.. There is some good documentation though and the
examples, while a bit too complex at first can be understood after
ahile. I hate having to relearn assembly though, it's been too long.
helloworld.pasm:
print "Hello World!\n"
Well...
Jason Gloudon wrote:
3) The vtable calls some code deletes the reference to the PMC, which is now
no longer accessible from the root set. The vtable then attempts to allocate
some memory.
The vtable function will now contain the only remaining reference to the PMC,
but unless the vtable function
On Jan-12, Nicholas Clark wrote:
> IIRC Leo added an option to Configure.pl to turn on optimising.
>
> Prior to this, on IRC Dan said to me that we need to avoid the hack that perl5
> found itself in, when it had to retro-fit the ability to change the compiler
> flags per file.
>
> Currently I do
At 11:21 AM -0500 1/13/03, Jason Gloudon wrote:
On a related note, I have been looking at implementation techniques for
incremental/generational garbage collectors. A critical aspect of a
generational garbage collector is a write barrier, which records any pointer
writes that create references to
On Jan-13, Jason Gloudon wrote:
> On Fri, Jan 10, 2003 at 01:05:05PM +0100, Leopold Toetsch wrote:
>
> > >While I'd like no stack walking, as it's pricey, I'm not sure it's
> > >tenable.
> >
> > As the current clone changes does show, it's possible.
> >
> > BTW current tests do succed w/o stac
Nicholas Clark wrote:
On Mon, Jan 13, 2003 at 05:14:54PM +0100, Leopold Toetsch wrote:
The -malign flags seem to have reasonable defaults.
As in you've read what they are, and they seem reasonable, or you've
actually tested the timings when playing with them?
The impact is very small, tho
Are you sure? I did it on mine and there was no segfault. My CVS copy is
from yesterday or the day before I think. I used the assemble.pl and
then called it helloworld.pbc and ran it with the parrot executable. I'm
still new to parrot and want to help out, but there is alot of stuff for
me to u
At 12:47 PM -0600 1/13/03, Joseph Guhlin wrote:
Are you sure? I did it on mine and there was no segfault. My CVS
copy is from yesterday or the day before I think. I used the
assemble.pl and then called it helloworld.pbc and ran it with the
parrot executable. I'm still new to parrot and want to
On Friday, January 10, 2003, 9:05:42 PM, you (mailto:[EMAIL PROTECTED]) wrote:
> Universe 2 (pro-unicode): "If we had a Unicode 'squiggly arrow' operator,
> then however it looks on everybody's display, it ought to at least look like
> some kind of squiggly arrow."
U+21DC "Leftwards Squiggle Arr
On Sun, Jan 12, 2003 at 11:50:14AM +, Richard J Cox wrote:
>
> U+21DC "Leftwards Squiggle Arrow" and U+21DE "Rightwards Squiggle Arrow" would
> seem to fit the bill rather well maybe the ascii <~ and ~> are merely
> aliases of the true symbols?
If we go this route, I would suggest that w
Dan Sugalski <[EMAIL PROTECTED]> writes:
> At 1:10 PM + 1/6/03, Piers Cawley wrote:
>>Dan Sugalski <[EMAIL PROTECTED]> writes:
>>> An object is a data type, as much as an array or hash is a data type,
>>> but that doesn't make an array an object. [insert obligatory "all men
>>> are Socrates
--- David Storrs <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 12, 2003 at 11:50:14AM +, Richard J Cox wrote:
> >
> > U+21DC "Leftwards Squiggle Arrow" and U+21DE "Rightwards Squiggle Arrow"
> would
> > seem to fit the bill rather well maybe the ascii <~ and ~> are merely
> > aliases of the tru
Mr. Nobody wrote:
Unicode operators in the core are a very, very, very, very, very, very, very,
very, very, very, very, very, very bad idea.
We've already had this discussion. We wouldn't be bringing up using
unicode operators for this function if we hadn't already talked about
unicode oper
--- Buddha Buck <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
>
> >
> > Unicode operators in the core are a very, very, very, very, very, very,
> very,
> > very, very, very, very, very, very bad idea.
>
> We've already had this discussion. We wouldn't be bringing up using
> unicode operators
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> --- Buddha Buck <[EMAIL PROTECTED]> wrote:
> > Mr. Nobody wrote:
> >
> > >
> > > Unicode operators in the core are a very, very, very, very, very,
> very,
> > very,
> > > very, very, very, very, very, very bad idea.
> >
> > We've already had this di
At 6:35 PM + 1/13/03, Piers Cawley wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
At 1:10 PM + 1/6/03, Piers Cawley wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
An object is a data type, as much as an array or hash is a data type,
but that doesn't make an array an object. [ins
--- Thom Boyer <[EMAIL PROTECTED]> wrote:
> Mr. Nobody <[EMAIL PROTECTED]> says:
> > Unicode operators in the core are a very, very, very, very, very, very,
> very,
> > very, very, very, very, very, very bad idea.
>
> OK, now I think I know how _you_ would vote on the subject of Unicode
> operator
At 10:52 AM -0800 1/13/03, Austin Hastings wrote:
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
--- Buddha Buck <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
>
> >
> > Unicode operators in the core are a very, very, very, very, very,
very,
> very,
> > very, very, very, very, very, very bad
--- Buddha Buck <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
> > --- Buddha Buck <[EMAIL PROTECTED]> wrote:
> >
> >>Mr. Nobody wrote:
> >>
> >>
> >>>Unicode operators in the core are a very, very, very, very, very, very,
> >>
> >>very,
> >>
> >>>very, very, very, very, very, very bad idea.
> >>
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 10:52 AM -0800 1/13/03, Austin Hastings wrote:
> >--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> >> --- Buddha Buck <[EMAIL PROTECTED]> wrote:
> >> > Mr. Nobody wrote:
> >> >
> >> > >
> >> > > Unicode operators in the core are a very, very, very
At 11:19 AM -0800 1/13/03, Austin Hastings wrote:
So the real question should be "What kind of upgrade path are we
providing for converting these tired old multigraphs into single
uniglyphs?"
Ah, that's a different question. Having Unicode synonyms may well be
considered reasonable thing, thoug
On Mon, Jan 13, 2003 at 09:51:13AM -0800, Steve Fink wrote:
> > reference or being a member of an aggregate.
> >
> > 2) A vtable function obtains a PMC* to that PMC.
> >
> > 3) The vtable calls some code deletes the reference to the PMC, which is now
> > no longer accessible from the root set. T
Ah, very cool. I did not know that.
--Joseph
http://www.josephguhlin.com/
Dan Sugalski wrote:
Yep, I'm sure. Without the end, parrot just falls off the end of the
world. If that happens to be into memory filled with nulls, you're
fine, otherwise Nasty Things may happen.
Mr. Nobody wrote:
> --- Buddha Buck <[EMAIL PROTECTED]> wrote:
>
> > Mr. Nobody wrote:
> >
> > > --- Buddha Buck <[EMAIL PROTECTED]> wrote:
> > >
> > > > We've already had this discussion.
> > >
> > > So if we already talked about why they're such a terrible idea,
> > > why are people still pr
I'm having problems making off of the recent cvs snapshot. When
running Configure, I get the errors/output below. Could anyone
suggest a fix that I could try?
I am running windows 2kpro, with gcc under cygwin as my compiler.
Thanks,
Joseph F. Ryan
[EMAIL PROTECTED]
Output of :
Checking M
James Mastros wrote:
On 01/12/2003 4:41 AM, Leopold Toetsch wrote:
There might be additional problems with glibc, but the deviations in
JIT code timings are only caused by moving the loop by on byte
(crossing a 8 byte boundary).
Do we have enough metadata at JIT-time to pad locations that ge
40 matches
Mail list logo
