This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstrapping hppa64? CPP problem
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: dave at hiauly1 dot hia dot nrc dot ca
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 10 Jul 2002 17:02:40 -0700 (PDT)
- Subject: Re: Bootstrapping hppa64? CPP problem
> I filed a PR for the exact same problem on vax-dec-ultrix4.3. However,
> I couldn't duplicate it with a cross compiler. It appears '!' isn't
> being processed correctly.
I am trying to dig into this some more and I don't think it is in the
'!' code. I am currently looking at eval_token, being called from
_cpp_parse_expr, being called from do_if and am looking at the symbol
_SVID2 in eval_token.
On a system where things work I get into 'case CPP_NAME' inside
eval_token and find that the if statement:
if (token->val.node == pfile->spec_nodes.n_defined)
is true and we call parse_defined and return the correct value.
On hppa64 I get to the same location in the code and find that this if
statement is false and the two pointers are not the same. I was
wondering if it was a 64 bit issue with the cpp hash table or something?
Is vax-dec-ultrix4.3 64 bits? The two values I see being compared
aren't even remotely close on hppa64 and look to be in different sections.
(gdb) p token->val.node
$1 = (struct cpp_hashnode *) 0x5f696e5f6e756c6c
(gdb) p pfile->spec_nodes.n_defined
$2 = (struct cpp_hashnode *) 0x80000001000c6030
pfile->spec_nodes.n_defined looks like a basic 64 bit data pointer on
hppa64 but token->val.node looks weird like it might be in text or
read-only memory somewhere.
Steve Ellcey
sje@cup.hp.com