From: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com>
To: "V Robert" <v_r_robert@rediffmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: need help
Date: Wed, 09 Jul 2003 18:42:00 -0000 [thread overview]
Message-ID: <x3u19vpmun.fsf@lifesupport.shutdown.com> (raw)
In-Reply-To: <20030708161540.11301.qmail@webmail24.rediffmail.com>
"V Robert" <v_r_robert@rediffmail.com> writes:
> Hi
> I'm porting GCC for a 16-bit target (i.e. the register size and
> memory operands are 16-bit). In the target header file, I've given
> #define INT_TYPE_SIZE 16
> #define LONG_TYPE_SIZE 16, etc
>
> My issue is that, for immediate operands greater than 16-bits, my
> ported compiler is giving "DImode" i.e. 8 bytes.
>
> For example, the below C statement
>
> int i=sizeof(0x10000);
>
> produces assembly which assigns 8 to i. BUT, i'm expecting 2 to be
> assigned for i. What should I do to make my ported compiler treat
> immediate values greater than 16-bits as HImode operand?
[snip]
I think you should re post this on gcc at gcc.gnu.org, where you are
likely to get better feedback on this sort of problem.
next prev parent reply other threads:[~2003-07-09 18:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 16:16 V Robert
2003-07-09 18:42 ` LLeweLLyn Reese [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 12:23 ASHA GOWDA
2007-06-07 14:53 ` Ian Lance Taylor
2005-03-21 8:54 arul kumaran
2005-02-08 12:19 Vijayalakshmic
2004-10-11 17:50 Need Help Sriharsha Vedurmudi
2004-10-13 7:16 ` Muthukumar Ratty
2003-10-01 5:23 need help cro
2003-10-01 6:10 ` Jeffrey Holle
2003-09-26 11:28 Eitan
2003-09-26 11:34 ` Jon Beniston
2002-08-19 10:07 Kitti Kittirutsunetorn
2002-08-19 12:02 ` bjorn rohde jensen
2002-08-19 14:56 ` Oscar Fuentes
2002-08-19 15:29 ` bjorn rohde jensen
2001-07-01 22:30 Need help Martin Kalen
2001-07-01 14:42 Jules FOSSO
2001-07-01 22:02 ` Parameshwari B.
2000-05-02 9:31 need help Claudiu BRASOVEAN
2000-05-02 10:00 ` llewelly
1999-11-05 13:05 Need Help Powell, Sandy
1999-11-30 23:28 ` Powell, Sandy
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=x3u19vpmun.fsf@lifesupport.shutdown.com \
--to=llewelly@lifesupport.shutdown.com \
--cc=gcc-help@gcc.gnu.org \
--cc=v_r_robert@rediffmail.com \
/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).