From: Andrew Haley <aph@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: Fwd: GCC label numbering
Date: Tue, 07 Sep 2010 13:21:00 -0000 [thread overview]
Message-ID: <4C863C38.6000409@redhat.com> (raw)
In-Reply-To: <AANLkTikpYMfBcpvz051EuDheP03ns+5hCe5Eks+z1GcY@mail.gmail.com>
On 09/07/2010 02:12 PM, Joel wrote:
> Hello,
> Apparently, at least for MIPS target, GCC generates labels starting
> from 2: $L2, $L3, etc.
> Do you know why the numbering begins at 2?
When I saw this question before, I thought that it'd be easy to find
out by debugging gcc. However, I also thought that there's no really
good reason why anyone would need the answer, so I didn't look.
You might get more response from others if you said why it's important
for you to know this.
Andrew.
next prev parent reply other threads:[~2010-09-07 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimb3Pn9As6huepyTDzwoYvvT4Vgr_RZ8EBYdcB7@mail.gmail.com>
2010-09-07 13:13 ` Joel
2010-09-07 13:21 ` Andrew Haley [this message]
2010-09-07 13:36 ` Joel
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=4C863C38.6000409@redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).