public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dean Povey <povey@dstc.qut.edu.au>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: alpha/OSF1 -g bug
Date: Tue, 11 Nov 1997 16:21:00 -0000	[thread overview]
Message-ID: <199711112325.JAA25204@typhoon.dstc.qut.edu.au> (raw)
In-Reply-To: <199711112319.SAA29795@subrogation.cygnus.com>

>   From: Dean Povey <povey@dstc.qut.edu.au>
>   Date: Wed, 12 Nov 97 09:15:12 +1000
>
>   >   From: Dean Povey <povey@dstc.qut.edu.au>
>   >   Date: Fri, 07 Nov 97 12:01:20 +1000
>   >
>   >   mips-tfile, /tmp/ccaauAsa.s:1421 String too big (4104 bytes)
>   >
>   >It's mips-tfile which is reporting the error.  That is part of egcs.
>   >You can probably just increase the size of PAGE_SIZE in mips-tfile.c
>   >to make it work again.  I'm not sure why mips-tfile.c has this fixed
>   >limit.
>   >
>
>   Nope, that breaks the compiler.
>
>   There must be a better way.
>
>Well, I don't know what it is.
>
>I do know that the error is coming from the mips-tfile program which
>is part of gcc.  It's not a bug in the OSF assembler, nor in gcc.
>

That is definitely right.  It is choking on this line of code:

STATIC symint_t
add_string (vp, hash_tbl, start, end_p1, ret_hash)
     varray_t *vp;                      /* string virtual array */
     shash_t **hash_tbl;                /* ptr to hash table */
     const char *start;                 /* 1st byte in string */
     const char *end_p1;                /* 1st byte after string */
     shash_t **ret_hash;                /* return hash pointer */
{
  register Ptrdiff_t len = end_p1 - start;
  register shash_t *hash_ptr;
  symint_t hi;

  if (len >= PAGE_USIZE)
    fatal ("String too big (%ld bytes)", (long) len);


I am  not up on the gcc architecture, but the comments in mips-tfile seem to 
indicate that because the strings are being stored in hash tables, they
can't exceed page boundaries.  This seems like a bit of a painful limitation
with the size of strings generated by C++ mangling of names.  I am not sure 
that
this is an easily fixed problem.

Thanks for your help anyway.
Dean.

-- 
Dean Povey,                             |  Email: povey@dstc.qut.edu.au 
Research Scientist, Security Unit,      |  Phone: +61 7 3864 2799 
CRC for Distributed Systems Technology  |  Fax:   +61 7 3864 1282
Queensland University of Technology     |  www.dstc.edu.au/events/roadshow/



       reply	other threads:[~1997-11-11 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199711112319.SAA29795@subrogation.cygnus.com>
1997-11-11 16:21 ` Dean Povey [this message]
1997-11-06 18:01 Dean Povey
1997-11-07  7:59 ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199711112325.JAA25204@typhoon.dstc.qut.edu.au \
    --to=povey@dstc.qut.edu.au \
    --cc=egcs@cygnus.com \
    --cc=ian@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).