Generate 64-bit friendly parser code?

[philippesigaud]

Generate 64-bit friendly parser code?

[PhilippeSigaud]

On Sat, Sep 8, 2012 at 1:17 PM, Chris Molozian [email protected]:

and I get the following errors during compilation (of the generated code):

src/parser.d(50): Error: cannot implicitly convert expression (tuple("Term",p.end)) of type Tuple!(string,ulong) to Tuple!(string,uint)
src/parser.d(55): Error: cannot implicitly convert expression (tuple("Term",p.end)) of type Tuple!(string,ulong) to Tuple!(string,uint)
src/parser.d(68): Error: cannot implicitly convert expression (tuple("Add",p.end)) of type Tuple!(string,ulong) to Tuple!(string,uint)
src/parser.d(73): Error: cannot implicitly convert expression (tuple("Add",p.end)) of type Tuple!(string,ulong) to Tuple!(string,uint)
// snip

But if I pass the -m32 option to the compiler it builds and links fine.
I'm not sure what the problem is, you can find the generated code (before
the -m32- flag) here: http://paste.ubuntu.com/1192434/

I use size_t for indices. AFAICT, that's what I'm supposed to to in D, to
get the correct type for indexing, be it for 32bits or 64bits, right?

Ah, drat, I found it, here is the culprit:

static TParseTree[Tuple!(string, uint)] memo;

I changed pegged/grammar.d accordingly and pushed the commit. Can you tell
me if it works?

[novabyte]

I removed the -m32 flag from my compiler options and re-ran the build against your latest change to master and it works splendidly. Thanks!

Fixed by 7e5a71e.

[PhilippeSigaud]

On Sat, Sep 8, 2012 at 3:07 PM, Chris Molozian [email protected]:

I removed the -m32 flag from my compiler options and re-ran the build
against your latest change to master and it works splendidly. Thanks!

Fixed by 7e5a71ehttps://github.com/PhilippeSigaud/Pegged/commit/7e5a71e2d1de1ebb1d67a6b2563d661ceb2595a4
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-8387403.

Cool! Does that mean it does not work with -m32?

[novabyte]

Sorry for the confusion, let me clarify the details.

After your latest code change Pegged successfully generates code that compiles with -m32 and -m64 (my default).

Thanks. :)

[PhilippeSigaud]

On Sat, Sep 8, 2012 at 3:21 PM, Chris Molozian [email protected]:

Sorry for the confusion, let me clarify the details.

After your latest code change Pegged successfully generates code that
compiles with -m32 and -m64 (my default).

Thanks. :)

Great! Thanks for sending bugs like this, this helps me tremdously, since I
tend to do my development on 32bits Linux.