From: Ian Lance Taylor <iant@google.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Andrew Haley <aph@redhat.com>,
Clem Taylor <clem.taylor@gmail.com>,
gcc-help@gcc.gnu.org
Subject: Re: workaround for "error: more than 30 operands in 'asm'"?
Date: Fri, 14 Mar 2008 15:13:00 -0000 [thread overview]
Message-ID: <m3bq5hqqyt.fsf@google.com> (raw)
In-Reply-To: <0f349aa3e2e8478152be585ff1934af6@kernel.crashing.org> (Segher Boessenkool's message of "Fri\, 14 Mar 2008 11\:22\:07 +0100")
Segher Boessenkool <segher@kernel.crashing.org> writes:
>> I wonder if we could do something more sensible than simply using the
>> constant 30. Perhaps some function of FIRST_PSEUDO_REGISTER, like
>> FIRST_PSEUDO_REGISTER+20, or FIRST_PSEUDO_REGISTER*2 or even
>> MAX (FIRST_PSEUDO_REGISTER, 29). This would at least solve the problem
>> here.
>
> Why is there a maximum here at all -- some hugely non-linear
> algorithm or so?
No, just a lot of statically defined arrays. Having a maximum doesn't
matter much; having a constant matters.
Ian
next prev parent reply other threads:[~2008-03-14 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 23:25 Clem Taylor
2008-03-13 5:56 ` Ian Lance Taylor
2008-03-13 9:45 ` Andrew Haley
2008-03-13 16:54 ` Ian Lance Taylor
2008-03-14 10:11 ` Andrew Haley
2008-03-14 10:22 ` Segher Boessenkool
2008-03-14 15:13 ` Ian Lance Taylor [this message]
2008-03-14 14:10 ` Ian Lance Taylor
2008-03-14 1:10 ` Clem 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=m3bq5hqqyt.fsf@google.com \
--to=iant@google.com \
--cc=aph@redhat.com \
--cc=clem.taylor@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).