public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sriharsha Vedurmudi <sriharsha.v@redpinesignals.com>
To: compilers@iecc.com, gcc-help@gcc.gnu.org
Subject: New datatype addition to gcc
Date: Fri, 10 Dec 2004 11:54:00 -0000	[thread overview]
Message-ID: <41B991F3.8060506@redpinesignals.com> (raw)

Hello All,

	I want to know if it is feasible (without too much of work) to add a new custom data-type to gcc 3.2.

We have a processor which originally has 16-bit addressing. So, while porting gcc3.2 to our processor, modifications were done to the effect 
that even character datatypes will access/address 16- bits. Now, our Processor development team says, they are adding 4 new instructions 
(load/store lo/high byte) and they want for the compiler to provide a provision where 8-bit addressing is possible in parallel with 16-bit, 
but NO 8-bit arithmetic is needed.
So, I thought, if a new custom-datatype can be added to the existing port, and only load/store functions can be attached to the variables of 
that datatype, it would be much simpler.

Please advice,
Thanks and Regards,
Sriharsha.

-- 
  *****************************
  * Sriharsha Vedurmudi			
  * Software Engineer		
  *
  * Redpine Signals Inc.	
  * Gate #395, Plot 87,88			
  * Sagar Society, Road #2,
  * Banjara Hills,		
  * Hyderabad - 500 034			
  * www.redpinesignals.com	
  *							
  * +91-40-23559911  (Office)
  * +91-98851-37338  (Mobile)
  *****************************

             reply	other threads:[~2004-12-10 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 11:54 Sriharsha Vedurmudi [this message]
     [not found] ` <6.2.0.14.2.20041210060756.020c2c28@iplan-mn.corp.adobe.com>
2004-12-14 14:07   ` Sriharsha
     [not found] <04-12-052@comp.compilers>
     [not found] ` <m3llc03gzm.fsf@tiktok.the-meissners.org>
2004-12-14 20:41   ` Sriharsha

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=41B991F3.8060506@redpinesignals.com \
    --to=sriharsha.v@redpinesignals.com \
    --cc=compilers@iecc.com \
    --cc=gcc-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).