public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ben A. Abderrazek" <baa@sowa.is.uec.ac.jp>
To: help-gcc@gnu.org
Subject: GNU CC Compiler and machine register number
Date: Tue, 21 Dec 1999 20:21:00 -0000	[thread overview]
Message-ID: <386051B0.B30C46ED@sowa.is.uec.ac.jp> (raw)

Dear Helper,


I have already installed GNU CC 2.7.3.2 compiler.

My quesstion is: 

First:

Is it possible for  the above compiler to generate a code for more than
32 architectural
registers (lets say 64 or 128 registers). The idea which I have, is that
I have to change the register numbers parameter 
in  the machine descrion code from 32  to 64 or 128.

Second: 

If it is right, is it  only the machine description file I have to
change? or there are other files  I have to change too.



I really need some hints,
Many thanks,


Ben,

WARNING: multiple messages have this Message-ID

From: "Ben A. Abderrazek" <baa@sowa.is.uec.ac.jp>
To: help-gcc@gnu.org
Subject: GNU CC Compiler and machine register number
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <386051B0.B30C46ED@sowa.is.uec.ac.jp> (raw)
Message-ID: <19991231222400.Ng99TEfW4F3ny0SIgSLYHXKxVqs2uScSMP1Fd0q2wwo@z> (raw)

Dear Helper,


I have already installed GNU CC 2.7.3.2 compiler.

My quesstion is: 

First:

Is it possible for  the above compiler to generate a code for more than
32 architectural
registers (lets say 64 or 128 registers). The idea which I have, is that
I have to change the register numbers parameter 
in  the machine descrion code from 32  to 64 or 128.

Second: 

If it is right, is it  only the machine description file I have to
change? or there are other files  I have to change too.



I really need some hints,
Many thanks,


Ben,

             reply	other threads:[~1999-12-21 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-21 20:21 Ben A. Abderrazek [this message]
1999-12-31 22:24 ` Ben A. Abderrazek

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=386051B0.B30C46ED@sowa.is.uec.ac.jp \
    --to=baa@sowa.is.uec.ac.jp \
    --cc=help-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).