This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ASM_GENERATE_INTERNAL_LABEL synopsis ?
- To: Mike Stump <mrs@wrs.com>
- Subject: Re: ASM_GENERATE_INTERNAL_LABEL synopsis ?
- From: Marc Espie <espie@tetto.liafa.jussieu.fr>
- Date: Tue, 31 Aug 1999 23:02:36 +0200
- Cc: Marc.Espie@liafa.jussieu.fr, egcs@egcs.cygnus.com
- References: <199908311811.LAA10292@kankakee.wrs.com>
- Reply-To: Marc.Espie@liafa.jussieu.fr
On Tue, Aug 31, 1999 at 11:11:00AM -0700, Mike Stump wrote:
> > Date: Tue, 31 Aug 1999 19:33:58 +0200
> > From: Marc Espie <espie@tetto.liafa.jussieu.fr>
>
> > Looking at dwarf2out.c, I believe that ASM_GENERATE_INTERNAL_LABEL
> > and its twins may be currently badly defined.
>
> Do you use values beyond 2 billion? If not, why worry about it? If
> so, can they be squished by the user to be less? If not, how big is
> the input to the compiler, and how large is the output?
> I think we want to skip playing with unsigned and go straight to long
> long if needed, I just question the need.
What is not at all funny is that, currently, we get
printf("%d", unsigned_long_value);
depending on the target endianness, and the way it handles var-adic
functions, this may just be the source of obscure bugs in some
cross-compilers.
I agree that having local labels be unsigned long is a bit silly, but
this is definitely not the main point here.